Model Context Protocol · Developers

Connect ADA AI to your own tools (MCP)

MCP (Model Context Protocol) is an open standard that lets AI assistants and developer tools talk to outside services. Once you connect ADA AI's MCP server, you can give the ADA AI team a task, follow its progress and fetch the finished report from the assistant or code editor you already use, without opening the app.

What you can do

ToolWhat it doesScope needed
start_taskGives the team a new task. You write the objective; context and brand are optional.tasks:run
get_task_statusShows which stage the task is in and the status of each step.tasks:read
get_task_reportReturns a finished task's report in Markdown.tasks:read
run_specialistSends a question or short job straight to a single specialist.specialists:run
list_brandsLists the brand profiles in your account, so you can pick one for a task.brands:read

How to connect

  1. Account settings → MCP Access Keys section in ADA AI.
  2. Create new key, name it (for example "Laptop · Claude Code") and choose the scopes you need. We recommend selecting only the scopes you'll use.
  3. The key is shown only once. Copy it right away and store it somewhere safe.
  4. In your MCP client, add a new HTTP server:
    URL: https://api.getadaai.com/api/v1/mcp
    Header: Authorization: Bearer <YOUR_KEY>
Example, Claude Code:
claude mcp add --transport http ada-ai https://api.getadaai.com/api/v1/mcp --header "Authorization: Bearer <YOUR_KEY>"
Example, run_specialist call (specialist slug):
{
  "name": "run_specialist",
  "arguments": {
    "specialist": "copywriter",
    "prompt": "Write a short launch email for my new product."
  }
}

Note: the specialist field accepts the specialist slug/key (e.g. copywriter, strategy, seo, analytics).

For other clients, check their documentation for adding an 'HTTP server' or 'remote MCP server'. Clients that only connect through OAuth aren't supported yet.

Good to know

01.Your account's rules still apply

Tasks started over MCP count toward your plan's task allowance, and the same daily and rate limits apply as in the app.

02.Actions that need approval still wait for you

If a task proposes something like creating a document in Drive or sending an email, it can't be approved over MCP. The approval card appears in ADA AI, and nothing happens until you approve it.

03.You only reach your own data

A key can only see your own tasks, reports and brands; cross-account data isolation is strictly enforced.

04.Don't share your key

Anyone with your key can act on your behalf within the scopes you chose. If you lose a device or suspect a key has leaked, revoke it on the same page; a revoked key stops working immediately.

05.Keys are stored hashed

We can't see your key in plain text either, so if you lose it you'll need to create a new one.

Questions or feedback?

For questions or suggestions regarding MCP integration, reach out to us at: [email protected]