Skip to main content
Concord is available as a remote Model Context Protocol (MCP) server. Any MCP client can ask the Concord agent about your campaigns, request changes, and hand it files, from inside its own conversation.
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.
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.

​
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, your Skills, brands, and memory. Ask it anything you would ask in a conversation:
Changes on your advertising platforms follow the same rules as in the web app. Concord prepares a platform action and nothing reaches a DSP before you approve it in Concord.

​
The tools

​
Where to go next

Connect a client

Claude Code, Claude Desktop, or any MCP client. How authorization works and what you approve.

Ask Concord

The askConcord tool: conversations, statuses, and how to recover a slow answer.

Upload files

Hand Concord a brief, a media plan, or a creative in three steps.

Limitations and troubleshooting

What the server does not do yet, and what common errors mean.