Skip to main content

Setting Up MagicPod MCP Server

  • Updated

Note
With the release of version 1.69.0, we have revamped our MCP server. As of version 1.75.0, support for the previous MCP server has been discontinued. If you are still using the previous MCP server, please refer to the setup instructions below to switch to the new MCP server.

 

Table of Contents

  1. Introduction
  2. Setup Instructions by Service
    1. ChatGPT
    2. Claude (Desktop, Web, Mobile)
    3. Claude Code
    4. Copilot CLI
    5. Microsoft Copilot Studio
    6. Codex
    7. Cursor
    8. Gemini — Antigravity / Gemini CLI / Gemini Enterprise
  3. Configuring Tool Permissions
  4. Troubleshooting

 

Introduction

The MagicPod MCP server URL is as follows.

Setup is complete once you configure this URL in your AI client and authenticate with MagicPod.

https://app.magicpod.com/mcp

 

Note for customers using two-factor authentication
If you have previously set up two-factor authentication, you may be asked to reconfigure your one-time password when using the MCP server. We apologize for the inconvenience; please follow the on-screen instructions to reconfigure it, then proceed with the MCP server setup again.

 

Setup Instructions by Service

ChatGPT

The setup procedure differs depending on how you log in to MagicPod.

If you log in with email (username) and password

Add the MagicPod MCP server as a custom MCP app. The configuration method differs depending on your ChatGPT plan.

Because the MagicPod MCP server has not yet been reviewed by OpenAI, it must be registered as a custom MCP app. The review is currently in progress, and a simpler setup procedure will be available soon.

  • Business plan

    A workspace Admin or Owner must first create the custom app and publish it to the workspace.

    • The Admin or Owner opens Workspace settings > Apps and clicks Create.
    • Enter the following to create the MagicPod app.
      • Name: MagicPod
      • MCP server URL: https://app.magicpod.com/mcp
    • Publish the created MagicPod app to the workspace.

    • Each member then selects the published MagicPod app and completes authorization by logging in on the MagicPod login screen that appears when connecting.

       

  • Enterprise / Edu plans

    A workspace Admin or Owner must configure permissions to allow the use of custom apps.

    • The Admin or Owner grants permission to use Developer mode to the relevant users as needed.
    • Users who have been granted permission open Settings > Apps > Advanced settings and enable Developer mode.
    • From Settings > Apps, click Create app, then enter the following to create it.
      • Name: MagicPod
      • MCP server URL: https://app.magicpod.com/mcp

    • When connecting to MagicPod, the MagicPod login screen opens in your browser. Log in to complete authorization.

       

  • Pro plan

    * On the Pro plan, features available via MCP are limited to read-only operations.

    • In ChatGPT, open Settings > Apps > Advanced settings and enable Developer mode.
    • From Settings > Apps, click Create app.
    • Enter the following to create it.
      • Name: MagicPod
      • MCP server URL: https://app.magicpod.com/mcp
    • When connecting to MagicPod, the MagicPod login screen opens in your browser. Log in to complete authorization.

     

  • Free / Go / Plus plans

    Custom MCP apps are not available. We plan to support these plans soon by registering MagicPod as a standard (non-custom) MCP app in the App Directory. 

 

If you log in with single sign-on (SAML) or GitHub

Connecting via single sign-on (SAML) or GitHub authentication is not currently supported. Support is coming soon.

 

Claude (Desktop, Web, Mobile)

The setup procedure differs depending on how you log in to MagicPod.

If you log in with email (username) and password

The MagicPod MCP server is listed as a Community connector in Claude's connector directory. By adding it from the directory, you can set it up without entering the URL manually.

MagicPod connector page: https://claude.ai/directory/magicpod

The configuration method differs depending on your Claude plan.

  • Team / Enterprise plans

    The Owner of your Claude Team / Enterprise organization must first add the connector to the organization.

    1. The Owner either opens Organization settings > Connectors and searches for "MagicPod", or opens the connector page directly, then adds it to the organization.
    2. Each member finds MagicPod (labeled "Custom") under Customize > Connectors, clicks Connect, and logs in to MagicPod.

     

  • Free / Pro / Max plans
    1. Either open Customize > Connectors in Claude and search for "MagicPod", or open the connector page directly, then click Connect to Claude.
    2. The MagicPod login screen opens in your browser. Log in to complete authorization.

If you log in with single sign-on (SAML) or GitHub

  1. Open Claude Desktop and go to Settings > Developer > Edit Config.

  2. The claude_desktop_config.json file will open. Add the following configuration to the file. Replace YOUR_API_TOKEN with the actual value of your MagicPod API token.

    {
  "mcpServers": {
    "magicpod": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.magicpod.com/mcp",
        "--header",
        "Authorization:Bearer YOUR_API_TOKEN"
      ]
    }
  }
}

  3. Save the file and restart Claude Desktop.

     

Claude Code

The setup procedure differs depending on how you log in to MagicPod.

If you log in with email (username) and password

Run the following command in your terminal.

claude mcp add --transport http magicpod https://app.magicpod.com/mcp && claude mcp login magicpod

Setup is complete once you log in with your email (username) and password on the screen that appears.

 

If you log in with single sign-on (SAML) or GitHub / If you use it in a headless environment such as CI

Run the following command in your terminal. Replace YOUR_API_TOKEN with the actual value of your MagicPod API token.

claude mcp add --transport http magicpod https://app.magicpod.com/mcp --header "Authorization: Bearer YOUR_API_TOKEN"

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Copilot CLI

The setup procedure differs depending on how you log in to MagicPod.

If you log in with email (username) and password

  1. Run the following command in your terminal.

    copilot mcp add --transport http magicpod https://app.magicpod.com/mcp

  2. Start Copilot CLI and run the following command.

    /mcp auth magicpod
  3. The MagicPod login screen opens in your browser. Log in to complete authorization.

* Connecting via OAuth requires Copilot CLI 1.0.15 or later. If your authentication expires, you can log in again with /mcp auth magicpod.

 

If you log in with single sign-on (SAML) or GitHub / If you use it in a headless environment such as CI

Run the following command in your terminal. Replace YOUR_API_TOKEN with the actual value of your MagicPod API token.

copilot mcp add --transport http --header "Authorization: Bearer YOUR_API_TOKEN" magicpod https://app.magicpod.com/mcp

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Microsoft Copilot Studio

In Microsoft Copilot Studio, you can add the MagicPod MCP server as a tool for your agent.

If you log in with email (username) and password

  1. Open Copilot Studio, go to Agents in the left menu, and open the agent you want to add the MagicPod MCP server to.
  2. On the Build tab, click + next to Tools on the right side.
  3. On the Add a tool screen, click + Add and select Model Context Protocol (MCP).
  4. On the Add MCP server screen, enter the following and click Add.
    • Server name: Any name (e.g., MagicPod)
    • Server description: Any description
    • Server URL: https://app.magicpod.com/mcp
    • Authentication: OAuth 2.0
    • Configuration type: Dynamic (with discovery)
  5. On the Select a connection screen, open the Connection drop-down and select Create new connection.
  6. Click Create.
  7. The MagicPod login screen opens in your browser. Log in to complete authorization.
  8. Once the connection appears under Connection, click Add. Setup is complete when MagicPod appears under Tools.

 

If you log in with single sign-on (SAML) or GitHub

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Codex

Codex CLI, the Codex IDE extension, and the Codex app share the same configuration file (~/.codex/config.toml), so an MCP server added from the CLI using the steps below is available in all of them.

The setup procedure differs depending on how you log in to MagicPod.

If you log in with email (username) and password

  1. Run the following command in your terminal.

    codex mcp add magicpod --url https://app.magicpod.com/mcp

  2. The MagicPod login screen opens in your browser. Log in to complete authorization.
    If the browser does not open automatically, if the command times out before you finish logging in, or if you need to log in again, run the following command.

    codex mcp login magicpod

 

If you log in with single sign-on (SAML) or GitHub / If you use it in a headless environment such as CI

  1. Set your MagicPod API token as an environment variable. Replace YOUR_API_TOKEN with the actual value of your MagicPod API token.

    export MAGICPOD_API_TOKEN=YOUR_API_TOKEN

  2. Run the following command in your terminal.

    codex mcp add magicpod --url https://app.magicpod.com/mcp --bearer-token-env-var MAGICPOD_API_TOKEN

To keep the environment variable across sessions, add the export line to your shell profile (e.g., ~/.zshrc or ~/.bashrc).

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Cursor

The setup procedure differs depending on how you log in to MagicPod. In either case, first open Cursor's MCP configuration file.

  • To use it in all projects: ~/.cursor/mcp.json
  • To use it only in a specific project: .cursor/mcp.json in the project root

If you log in with email (username) and password

  1. Add the following configuration to the MCP configuration file and save it.

    {
  "mcpServers": {
    "magicpod": {
      "url": "https://app.magicpod.com/mcp"
    }
  }
}
  2. From the Cursor sidebar, open Customize > MCPs and click Authenticate for MagicPod.
  3. The MagicPod login screen opens in your browser. Log in to complete authorization.

If you use Cursor CLI, save the configuration file above, then run the following command in your terminal to log in.

agent mcp login magicpod

 

If you log in with single sign-on (SAML) or GitHub / If you use it in a headless environment such as CI

  1. Add the following configuration to the MCP configuration file. Replace YOUR_API_TOKEN with the actual value of your MagicPod API token.

    {
  "mcpServers": {
    "magicpod": {
      "url": "https://app.magicpod.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
  2. Restart Cursor.

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Gemini — Antigravity / Gemini CLI / Gemini Enterprise

Note
The Gemini app (gemini.google.com) does not support the MagicPod MCP server. To use the MagicPod MCP server from Gemini, please use Antigravity (Antigravity IDE / Antigravity 2.0), Gemini CLI, or Gemini Enterprise.

Antigravity

Open the MCP configuration file (mcp_config.json). In Antigravity IDE, you can open it from the agent panel via … > MCP Servers > Manage MCP Servers > View raw config.

The setup procedure differs depending on how you log in to MagicPod.

If you log in with email (username) and password

  1. Add the following configuration and save it.

    {
  "mcpServers": {
    "magicpod": {
      "serverUrl": "https://app.magicpod.com/mcp"
    }
  }
}
  2. Open Settings (Cmd+, on macOS, Ctrl+, on Windows/Linux), go to the Customizations tab, and click Authenticate next to MagicPod.
  3. The MagicPod login screen opens in your browser. After logging in to complete authorization, copy the authorization code that is displayed, paste it into the Antigravity settings screen, and click Submit.

 

If you log in with single sign-on (SAML) or GitHub / If you use it in a headless environment such as CI

  1. Add the following configuration. Replace YOUR_API_TOKEN with the actual value of your MagicPod API token.

    {
  "mcpServers": {
    "magicpod": {
      "serverUrl": "https://app.magicpod.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
  2. Save the configuration and restart Antigravity.

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Gemini CLI

The setup procedure differs depending on how you log in to MagicPod.

If you log in with email (username) and password

  1. Run the following command in your terminal.

    gemini mcp add --scope user --transport http magicpod https://app.magicpod.com/mcp

  2. Start Gemini CLI and run the following command.

    /mcp auth magicpod
  3. The MagicPod login screen opens in your browser. Log in to complete authorization.

 

If you log in with single sign-on (SAML) or GitHub / If you use it in a headless environment such as CI

Run the following command in your terminal. Replace YOUR_API_TOKEN with the actual value of your MagicPod API token.

gemini mcp add --scope user --transport http --header "Authorization: Bearer YOUR_API_TOKEN" magicpod https://app.magicpod.com/mcp

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Gemini Enterprise

In Gemini Enterprise, you can add the MagicPod MCP server as a custom MCP server data store (data connector).

If you log in with email (username) and password

The Gemini Enterprise administrator must first create the data store in the Google Cloud console and enable its actions (the tools of the MagicPod MCP server).

What the administrator does

  1. Configure the required settings in Google Cloud. For details, see "Set up your custom MCP server data store — Before you begin" in the Gemini Enterprise documentation.

  2. Create the data store by following "Create the custom MCP server data store" in the Gemini Enterprise documentation. Select OAuth 2.0 as the authentication method and enter the following values:

    • MCP Server URL: https://app.magicpod.com/mcp
    • Authorization URL: https://app.magicpod.com/api/magicpod/authorize
    • Token URL: https://app.magicpod.com/api/magicpod/token
    • Client ID: magicpod-gemini-enterprise
    • Client Secret: Leave empty
    • Scopes: openid email profile
    • Enable PKCE Support: On
    • Use HTTP Basic Authentication: Off (it is selected by default, so clear the checkbox)

    When you click Verify Auth, a MagicPod sign-in window opens. Click Sign in to MagicPod, log in to MagicPod, and complete the authorization.

  3. When the state of the data store changes to Active, click Reload custom actions on the Actions tab of the data store. If this fails, authenticate again and retry.
  4. Select the actions you want to enable, and click Enable actions.

What each member does

  1. Open Gemini Enterprise and click the Connectors icon below the chat input field.
  2. Under Custom MCP, find the MagicPod data store (shown with the name set by the administrator) and click Authorize.
  3. A MagicPod sign-in window opens. Click Sign in to MagicPod, log in to MagicPod, and complete the authorization.
  4. When the toggle for the MagicPod data store is on, the setup is complete.

 

If you log in with single sign-on (SAML) or GitHub

We plan to support setup for single sign-on (SAML) and GitHub authentication using the same procedure as email/password soon.

 

Configuring Tool Permissions

Depending on the AI agent you use, you can configure permissions for individual tools provided by the MagicPod MCP server.

For example, in Claude Desktop, you can configure permissions for each tool from the MagicPod MCP server connector settings. You can choose to always allow the tool, require approval each time it is used, or deny access to it.

Restricting certain tools may limit the operations the AI agent can perform or reduce its accuracy. Therefore, we generally recommend enabling all tools and setting their permissions to "Always allow."

However, your organization may have security policies or operational guidelines regarding the use of AI agents. Please configure tool permissions as needed to comply with these policies and guidelines.

 

Troubleshooting

If a connection error or authentication error occurs

Make sure your API token is correct and has not expired, and that https://app.magicpod.com is accessible from your network. If necessary, issue a new token from the MagicPod settings screen.

 

If you cannot connect after logging in through the browser / If you need to log in again

If your authentication has expired, or if you want to switch to a different MagicPod account, log in again as follows.

  • Claude Code: claude mcp login magicpod
  • Copilot CLI: run /mcp auth magicpod inside Copilot CLI
  • Codex: run codex mcp logout magicpod, then codex mcp login magicpod
  • Cursor CLI: agent mcp login magicpod
  • Gemini CLI: run /mcp auth magicpod inside Gemini CLI

Browser login cannot be completed in environments where a browser is not available (such as over SSH or inside a container). In those environments, set up the connection using the API token procedure instead.

 

If npx: command not found is displayed

Install Node.js (version 18 or later). npx is included with Node.js.

 

If an error appears while a response is being generated

For example, if you are using the free version of Claude, the error "Claude's response was interrupted." may appear while a response is being generated. This is caused by the character limit on the free version and can be avoided by using the paid Claude Pro plan. Similar issues may occur with other AI agents, so please consider subscribing to a paid plan.

 

 

Was this article helpful?
0 out of 0 found this helpful
If the problem persists, please contact us from here.
Contact
Return to top

Related articles