Skip to main content
Aide’s MCP server lets AI assistants such as Claude and ChatGPT work in your Aide workspace: search your knowledge, look up Shopify orders, read and reply to conversations, and ask for refunds, all as you and within your role. MCP (Model Context Protocol) is the open standard AI assistants use to connect to other tools. Every action an assistant takes through Aide is a call to the Aide API, with the same permissions, approval rules and limits as the dashboard. The server address for every app is:

Which apps can connect

Signing in connects the app as you: it sees what you can see in Aide and its actions are recorded as yours. An API key connects as the workspace and never sees conversations: a read-only key reads knowledge, products, topics, macros, orders and analytics, and a key that can also write can edit articles, topics and procedures. MCP is available on every Aide plan, and before a plan starts. What an app can do still depends on your role: it acts as you, within the approval limits you have in Aide.

Connect Claude

The easiest way is Claude’s connectors directory: open claude.ai/directory/aide and add Aide from there, with no server address to type. When Aide opens, sign in, check the workspace and the permissions, and select “Approve”. You can also add Aide as a custom connector. Claude’s custom connectors work on Claude’s Free, Pro, Max, Team and Enterprise plans. Claude Free allows one custom connector. On Pro or Max:
  1. In Claude, go to Customize > Connectors.
  2. Select ”+ Add”, then “Add custom connector”.
  3. Name it Aide, enter https://app-api.aide.app/mcp and select “Continue”.
  4. Review the authentication settings Claude detected and select “Continue”.
  5. Under Authentication, choose “Sign in now”.
  6. Under OAuth client, choose “Register automatically”.
  7. Select “Add”. When Aide opens, sign in, check the workspace and the permissions, and select “Approve”.
On Team or Enterprise, an owner first adds Aide under Organization settings > Connectors: select “Add”, hover over “Custom”, choose “Web”, and use the same address and settings. Each member then goes to Customize > Connectors, finds Aide and selects “Connect”. To use Aide in a chat, select ”+” in the message box, then “Connectors”, and turn Aide on. Claude asks for your approval before it uses a tool: check what a reply or an order change will do before you allow it. Claude’s own steps: Get started with custom connectors using remote MCP.

Connect ChatGPT

Aide is in ChatGPT’s plugin directory: open Aide in ChatGPT and install the plugin, with no server address to type. You can also find it by searching for Aide under Plugins in ChatGPT’s sidebar. ChatGPT asks you to connect Aide, either as you install the plugin or the first time you use it. When Aide opens, sign in, check the workspace and the permissions, and select “Approve”. To use Aide in a chat, type @ and choose Aide. ChatGPT also turns to Aide on its own when your request calls for it, and asks you to confirm before Aide sends a reply or changes an order. ChatGPT’s company knowledge and deep research can also use Aide’s search tools to read your knowledge. In a ChatGPT Business, Enterprise or Edu workspace, an admin decides which plugins members can install. If Aide shows as disabled there, ask your admin to make it available. If you added Aide by hand as a custom MCP server before it was in the directory, that connection keeps working. OpenAI’s steps: Plugins in ChatGPT.

New to Aide?

After you approve, open a new chat with Aide turned on and send “Set up Aide for my business”. Claude checks what’s left and does each step for you: it teaches Aide your website, tests your agent and gets your chat or email ready, and asks only for what it needs from you: a few facts and pasting the chat snippet. If your agent isn’t deployed, it asks for your OK before deploying it. ChatGPT does the same once you choose Aide with @.

Connect Claude Code

Run:
Then type /mcp in Claude Code, choose aide and sign in to Aide in the browser window that opens. You can also run claude mcp login aide from your shell. To use an API key instead, add --header "Authorization: Bearer <your API key>" to the command. If the key is rejected, Claude Code doesn’t fall back to signing in; remove the header to sign in instead. Anthropic’s steps: Connect Claude Code to tools via MCP.

Connect Codex

Add Aide to ~/.codex/config.toml:
Then run codex mcp login aide and sign in to Aide in your browser. In the ChatGPT desktop app (Settings > MCP servers) or the Codex IDE extension (gear menu > MCP servers) you can instead select “Add server”, choose Streamable HTTP, enter the address, save and restart, then select “Authenticate”. To use an API key instead, add bearer_token_env_var = "AIDE_API_KEY" under [mcp_servers.aide] and set AIDE_API_KEY in your environment. OpenAI’s steps: Codex: Model Context Protocol.

Connect Gemini CLI

Run:
Then type /mcp auth aide in Gemini CLI and sign in to Aide in your browser. To use an API key instead, add --header "Authorization: Bearer <your API key>" to the command. Gemini CLI saves the header in ~/.gemini/settings.json, so keep that file private. Google’s steps: MCP servers with the Gemini CLI.

Connect Cursor

Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
Then open Customize in Cursor’s sidebar, find aide and sign in to Aide in the browser window that opens. For Cloud Agents, a team admin adds Aide as a Team MCP server under Dashboard > Plugins & MCPs in Cursor, with the same address. To use an API key instead, create a read-only key (see API keys and webhooks), set it as AIDE_API_KEY in your environment, and add the header to the server:
Cursor’s steps: Model Context Protocol (MCP).

Connect VS Code

  1. Open the Command Palette and run “MCP: Add Server”.
  2. Choose “HTTP (HTTP or Server-Sent Events)” and enter https://app-api.aide.app/mcp.
  3. Enter a server ID, such as aide.
  4. For a personal setup, select “Global”, then “Copilot Global”.
  5. When VS Code asks you to sign in, sign in to Aide in your browser, check the workspace and the permissions, and select “Approve”.
To use an API key instead, create a read-only key (see API keys and webhooks) and add this to .vscode/mcp.json in your workspace; VS Code asks for the key the first time the server starts and stores it securely:
VS Code doesn’t pass servers that ask for a value like this to its Copilot harness sessions, so use Aide from a Local session. Microsoft’s steps: Add MCP servers in VS Code and the MCP configuration reference.

Connect Perplexity

Perplexity offers custom remote connectors to Enterprise organizations. Members can add one when an admin allows it, and admins can add one for the whole organization.
  1. For your own account, open Plugins in the sidebar (or Customize > Connectors if you don’t see Plugins), then Add custom > Connector > Add MCP connector. To add it for the organization, an admin goes to Enterprise settings > Permissions > Connectors permissions and clicks ”+ Custom connector”.
  2. In the pop-up, select Remote.
  3. Name it Aide and enter https://app-api.aide.app/mcp as the MCP Server URL.
  4. Set Authentication to OAuth and Transport to Streamable HTTP.
  5. Check the acknowledgement box and click “Add”.
  6. Click the connector card to sign in. When Aide opens, sign in, check the workspace and the permissions, and select “Approve”.
If an admin adds Aide for the organization, have each member sign in on their own rather than signing in once for everyone: Aide acts as whoever signed in. The admin then shares the connector from the Permissions screen in Enterprise settings. Perplexity’s steps: Adding Custom Remote Connectors.

Connect Devin and Gemini Enterprise

Devin (app.devin.ai): an organization admin adds Aide under Customize > MCPs > Add MCP > Add custom MCP, with transport HTTP, Server URL https://app-api.aide.app/mcp, authentication OAuth and Access set to Personal, so each teammate selects Connect and signs in as themselves. Devin’s steps: MCP servers and marketplace. Gemini Enterprise: a Google Cloud admin adds Aide as a Custom MCP Server data store with OAuth 2.0 (authorization URL https://app-api.aide.app/oauth/authorize, token URL https://app-api.aide.app/oauth/token, scopes aide:read aide:write, Enable PKCE Support ticked), using a client ID and secret created once by registering at https://app-api.aide.app/oauth/register with token_endpoint_auth_method set to client_secret_post and the redirect URI https://vertexaisearch.cloud.google.com/oauth-redirect. Google’s steps: Set up your custom MCP server data store.

Signing in and permissions

When an app signs in, Aide shows which app is asking, the workspace it will use and what it may do. Nothing is shared if you decline.
  • Read only (aide:read): read conversations, messages, knowledge, orders and analytics.
  • Read and act (aide:read aide:write): also add internal notes, update conversations, reply to customers, and ask for refunds and cancellations, which follow your approval rules.
The app connects to the workspace shown on that screen, as you, within your role: it can do what you can do in Aide. Owners and admins can also change settings with it, such as setting Aide up, channels, helpdesk rules, billing and the team. Agents can’t change those settings, disconnect integrations or see analytics. The app’s own name is shown as the app chose it; Aide doesn’t verify it. Apps stay connected for 30 days after they were last used. Leaving the workspace or being deactivated cuts them off. API keys are created by owners and admins under Settings > Developers (see API keys and webhooks). A read-only key is enough for MCP; a key without read access is refused.

What the app can do

Read tools, for anyone connected: Any app, even a read-only one, can also use send_feedback to tell the Aide team when it couldn’t do what you asked or something looked wrong. It changes nothing in your workspace. Read tools for teammates who signed in: Tools that act, for teammates who signed in with read and act: Starting an email conversation needs a plan. A draft the app writes waits in your Drafts in Aide’s inbox, and nothing is emailed until you send it there or ask the app to send it (see Start an email conversation with a customer). Setup tools, for owners and admins (the ones that change something need read and act): In Claude and the other apps (not ChatGPT), the app can also reach the rest of Aide’s settings by area: topics, knowledge collections, analytics, channels, helpdesk rules, procedures and macros, more conversation and order actions, the team and billing. It looks up an area’s actions when it needs one, within your role, and changes are marked so the app asks you first. In ChatGPT, the other settings aren’t available: use Ask Aide in the dashboard, or Claude. ChatGPT has its own tools to read macros and analytics (owners and admins), and to manage procedures and your agent’s Instructions. Procedures work as in the dashboard: an app can create one and edit it until it first goes live. Once a procedure is live, the app’s edits wait in a draft until it sets the procedure live again, which keeps a version you can restore. It can also check a When to use on your recent conversations before setting it live. Setting procedures live, restoring versions, drafts, Check trigger and changing Instructions are for owners and admins. An app is shown only the tools its sign-in or key can use. Tools that send a message to a customer, update a conversation, change an order, reject an order change, replace saved settings, change Instructions or put your agent or a procedure live are marked as such, so Claude and ChatGPT can ask you before using them.

Limits

  • 300 MCP requests a minute per connection. Each tool call also counts against the API’s limits: 600 a minute per sign-in or key and 3,000 a minute per workspace.
  • Knowledge searches share your workspace’s 60 a minute.
  • Apps can send the Aide team up to 30 notes a day per workspace.
  • When a limit is reached, the app is told how many seconds to wait.

Your data

  • Aide sends the app only the results of the tools it calls. The assistant’s provider (Anthropic, OpenAI, Google, Cursor, Microsoft, Perplexity, Cognition for Devin) handles those results under its own terms and your settings with it.
  • Aide doesn’t receive or keep your chats with the assistant. Notes, replies, updates and order requests made through the app are saved in Aide like any other, recorded as you.
  • When the app sends the Aide team a note with send_feedback, Aide removes email addresses, phone, card, tracking and order numbers before saving it. Only Aide’s team reads it.
  • Sign-in tokens last an hour and renew for up to 30 days; Aide stores them only in hashed form. Disconnecting deletes them straight away.

See and disconnect apps

Go to Settings > Developers. “Connected apps” lists the apps you’ve connected, whether each can read only or read and act, and when it was last used. Select Disconnect to cut an app off at once. You can also remove Aide from the app’s own settings (Customize > Connectors in Claude, the plugin’s settings in ChatGPT). Owners and admins revoke API keys from their row under Settings > Developers.

Troubleshooting

  • The app asks you to sign in again: the connection was disconnected, expired after 30 days without use, or you left the workspace. Connect again.
  • Conversations or replies are missing: you connected with an API key, which never sees conversations, or the app asked for read-only access. Disconnect and connect again; the consent screen shows whether the app is asking to read only or to read and act.
  • “insufficient_scope”: the app tried to act with a read-only connection. Reconnect with read and act.
  • Analytics are missing: analytics are for owners and admins.
  • Claude can’t finish connecting: remove the connector and add it again with OAuth client set to “Register automatically”.
  • ChatGPT shows old or missing tools: OpenAI checks each change to Aide’s tools before ChatGPT offers it, so a new tool can reach ChatGPT later than other apps. If you added Aide by hand as a custom MCP server, ChatGPT keeps the tool list from when it was added: refresh it from its settings page (on Business and Enterprise, an admin refreshes it in workspace settings).
  • A refund didn’t happen: it is waiting for approval because it is above your limits. An admin can approve it in Aide, or through approve_order_action.
  • “Too many requests”: wait the number of seconds the app reports.
  • Wrong workspace: disconnect the app, switch to the right workspace in Aide, and connect again.