> ## Documentation Index
> Fetch the complete documentation index at: https://docs.concord.ad/llms.txt
> Use this file to discover all available pages before exploring further.

# Concord MCP server

> Talk to the Concord agent from Claude, Cursor, or your own agent over the Model Context Protocol.

Concord is available as a remote [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server. Any MCP client can ask the Concord agent about your campaigns, request changes, and hand it files, from inside its own conversation.

```
https://api.concord.ad/mcp
```

There is nothing to provision: no API key, no client secret. Point your client at the URL, sign in to Concord when the browser opens, approve the connection, and the tools are available.

<Note>
  The MCP server is in early access. Connection and authorization are stable; the tool surface is deliberately small and will grow. Send feedback to [support@concord.ad](mailto:support@concord.ad).
</Note>

## What you can do with it

The server exposes the same Concord agent you use in the web app, with the same context: your connected platforms, your workspace [scope](/settings/managing-scope), your Skills, brands, and memory. Ask it anything you would ask in a conversation:

```
"How is the Q3 Retail campaign pacing on DV360 this week?"
```

```
"Pause every line item under 0.2% CTR on the Meta prospecting campaign."
```

```
"Build a media plan from the brief I just uploaded."
```

Changes on your advertising platforms follow the same rules as in the web app. Concord prepares a [platform action](/features/platform-actions/platform-actions-overview) and nothing reaches a DSP before you approve it in Concord.

## The tools

| Tool            | Purpose                                                                                                         |
| --------------- | --------------------------------------------------------------------------------------------------------------- |
| `askConcord`    | Send a message to the Concord agent and get its answer. Carries a `chatId` so a client can hold a conversation. |
| `prepareUpload` | Step 1 of giving Concord a file: returns a signed upload URL.                                                   |
| `attachUpload`  | Step 2: registers the uploaded bytes as a Concord file, optionally on a conversation.                           |

## Where to go next

<CardGroup cols={2}>
  <Card title="Connect a client" icon="link" href="/developers/mcp/connecting">
    Claude Code, Claude Desktop, or any MCP client. How authorization works and what you approve.
  </Card>

  <Card title="Ask Concord" icon="comments" href="/developers/mcp/ask-concord">
    The `askConcord` tool: conversations, statuses, and how to recover a slow answer.
  </Card>

  <Card title="Upload files" icon="file-arrow-up" href="/developers/mcp/uploading-files">
    Hand Concord a brief, a media plan, or a creative in three steps.
  </Card>

  <Card title="Limitations and troubleshooting" icon="triangle-exclamation" href="/developers/mcp/limitations">
    What the server does not do yet, and what common errors mean.
  </Card>
</CardGroup>