Connect an AI assistant to your Autogram data.

Every option below uses the same URL. Your AI app opens an Autogram screen, you sign in and click Allow, and it connects to that workspace. Disconnect any app anytime from Settings, then MCP.

https://api.autogram.co.in/mcp

Claude on web, desktop and mobile

Opens Claude's Add custom connector dialog with everything filled in. Click Add, then Connect, then Allow on the Autogram screen.

Add to Claude

ChatGPT

1. Open Settings, then Apps & Connectors, and turn on Developer mode under Advanced.
2. Choose Create, name it Autogram, and paste the URL below.
3. Keep authentication on OAuth, create it, then click Allow on the Autogram screen that opens.

Cursor and VS Code

One click installs the server. The editor then asks you to sign in to Autogram.

Add to CursorAdd to VS Code

Claude Code in the terminal

Run this, then type /mcp in Claude Code and choose Authenticate:

claude mcp add --transport http autogram https://api.autogram.co.in/mcp

Any other AI app

Paste this into it. An app that can add servers will connect itself. One that can't will tell you exactly where to click.

Connect the Autogram MCP server so you can work with my Instagram automations.

Server URL: https://api.autogram.co.in/mcp
Type: remote MCP (Streamable HTTP). Sign-in: OAuth — no API key; I will approve it in my browser.

- If you can run commands (Claude Code): run `claude mcp add --transport http autogram https://api.autogram.co.in/mcp`, then have me run /mcp and choose Authenticate.
- If you have an MCP config (Cursor, VS Code, Windsurf and similar): add a remote server named "autogram" with url https://api.autogram.co.in/mcp.
- If you can't add servers yourself (Claude or ChatGPT in a browser): tell me the exact clicks to add it as a custom connector in your settings.

Once it is connected, call workspace_summary to confirm it works.

Advanced: API keys

For scripts, CI, or an app that can't sign in with OAuth. Sign in, then Settings, then MCP, then Advanced, then Generate key. It starts with ag_live_ and should be treated like a password.

Clients that take a remote URL with headers (Cursor, Windsurf):

{
  "mcpServers": {
    "autogram": {
      "url": "https://api.autogram.co.in/mcp",
      "headers": {
        "Authorization": "Bearer ag_live_YOUR_KEY_HERE"
      }
    }
  }
}

Claude Desktop with a key, through the stdio bridge. A {url, headers} entry makes Desktop skip the whole file, so add this to claude_desktop_config.json, quit Desktop fully from the tray, then reopen:

{
  "mcpServers": {
    "autogram": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.autogram.co.in/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer ag_live_YOUR_KEY_HERE"
      }
    }
  }
}

Claude Code with a key:

claude mcp add --transport http autogram https://api.autogram.co.in/mcp --header "Authorization: Bearer ag_live_YOUR_KEY_HERE"

Never share a live key in a screenshot, a support ticket, or anywhere public. Regenerate it from the dashboard if you think it leaked, and the old one stops working straight away.