Connect an AI agent

CueDM runs an MCP server, the standard way AI apps connect to other tools. Connect Claude, ChatGPT, Cursor or Claude Code to it and you can ask, in your own words, for things like:

• “When people comment GUIDE on my latest reel, DM them the guide link.”
• “How did my protein guide automation do this month?”
• “Change the DM on my ABS automation and add a public reply.”
• “Add our refund policy to the knowledge base.”

The agent signs in as you, in the workspace you choose, so it sees what you see and nothing more. Automations it creates start switched off: it gives you a link to review each one, and turns one on only when you ask.

Every app needs the same address. When you add it, a CueDM window opens: sign in, pick the workspace and choose Allow. There is no key to copy.

https://cuedm.com/api/mcp

The quickest way: in CueDM open Settings → Integrations and choose Copy prompt on Connected AI apps. Paste it into your AI app and it walks you through the rest.

Claude

1. Add a custom connector

   In Claude (on the web, desktop or mobile), open Settings → Connectors and choose Add custom connector. Name it CueDM and paste the URL above.

2. Sign in to CueDM

   Choose Connect. Sign in to CueDM in the window that opens, pick the workspace and choose Allow.

3. Ask for something

   Start a chat and ask, for example, “List my CueDM automations.”

ChatGPT

Add CueDM as a custom connector (an MCP server) in ChatGPT's settings, with the URL above. Depending on your plan, ChatGPT may ask you to turn on developer mode first. Then sign in to CueDM when asked.

Claude Code

claude mcp add --transport http cuedm https://cuedm.com/api/mcp

Then run /mcp inside Claude Code and choose CueDM to sign in.

Cursor, VS Code and other MCP clients

Add a remote server with the URL. In Cursor, that's this in mcp.json:

{
  "mcpServers": {
    "cuedm": {
      "url": "https://cuedm.com/api/mcp"
    }
  }
}

The client finds the sign-in page by itself and opens it the first time it connects.

These are the tools the server offers. An agent connected with read-only access can only use the ones marked reads.

list_accountsreads

The workspace's connected Instagram accounts and their ids.

list_recent_postsreads

An account's recent posts and reels with captions, to pick the post an automation runs on.

list_automationsreads

The workspace's automations and whether each is on.

get_automationreads

One automation in full: trigger, DM, buttons, public replies, review link.

get_automation_resultsreads

Comments that triggered it, DMs sent and failed, link taps and tap rate, top keywords, over 7, 30 or 90 days.

list_knowledgereads

What the account's AI agents answer from, and whether each source is ready.

create_comment_automationchanges

A comment-to-DM automation on a post, any post or the next reel. Created switched off.

update_automationchanges

Change an automation's post, keywords, DM, link, public reply or name.

set_automation_activechanges

Turn an automation on or off. Only when the person has asked.

add_knowledgechanges

Add a Q&A, some text, web pages or the account's captions to the knowledge base.

It can't see billing, change your team, delete anything, or send a DM to someone directly: DMs only go out through automations, after someone comments.

readscope

See your Instagram accounts, posts, automations, their results and your knowledge base

writescope

Create and change automations, turn them on or off, and add to your knowledge base

• The agent acts as the person who connected it. If you're a member limited to some accounts, so is the agent, and if you leave the workspace it stops working.
• Everything it changes appears in Settings → Activity with the app's name, for example “Created automation … via Claude”.
• Disconnect it any time in Settings → Integrations under Connected AI apps. Owners and admins can disconnect anyone's.

For a script or a self-built agent that can't sign in through a browser, send a workspace API key (Studio) as a bearer token to the same URL. It acts as the workspace rather than a person. Authentication covers creating one.

{
  "mcpServers": {
    "cuedm": {
      "url": "https://cuedm.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${CUEDM_API_KEY}"
      }
    }
  }
}

The server speaks the 2026-07-28 MCP specification over Streamable HTTP, statelessly, and also answers 2025-era clients. Authorization follows the MCP authorization spec with OAuth 2.1:

DiscoveryRFC 9728, 8414

A request without a token gets 401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource, which names the authorization server; its metadata is at /.well-known/oauth-authorization-server.

Client identityCIMD, RFC 7591

Use an https URL to your client metadata document as the client_id (preferred), or register at /oauth/register. Redirect URIs must be https, loopback http (any port) or your app's own scheme.

Grantauthorization code

PKCE with S256 is required. Send resource=https://cuedm.com/api/mcp. The redirect carries iss (RFC 9207); codes are single-use and last five minutes.

Tokensopaque

Access tokens last 1 hour; refresh tokens 60 days and are replaced on every use. Presenting a used refresh token again ends the connection. Revoke at /oauth/revoke (RFC 7009).