Connect your AI agent

Every client connects to the same hosted Dynamoi MCP server at https://dynamoi.com/mcp and opens the Dynamoi sign-in page on first use. Which tools a client sees and which it may call depend on the client; the table below summarizes it, and Client permissions explains why.

Client	Tool catalog	Access
ChatGPT	Directory (24 tools)	Reads, Smart Link changes, and distribution applications
Claude added from the directory listing	Directory (24 tools)	Reads, Smart Link changes, and distribution applications
Claude on the web or desktop (custom connector)	Full (38 tools)	Full access, including launches and budget changes
Claude Code	Full (38 tools) on /mcp; directory through the Dynamoi plugin	Full access
Codex CLI	Full (38 tools)	Full access
Cursor, VS Code, Gemini CLI, OpenClaw	Full (38 tools)	Full access
Unreviewed web apps and any other client	Directory (24 tools)	Reads, Smart Link changes, and distribution applications

ChatGPT

1. Open the Dynamoi app Open Dynamoi from the ChatGPT app directory. In ChatGPT developer mode you can instead add a custom app with the MCP server URL https://dynamoi.com/mcp and OAuth authentication.

2. Approve access Sign in to Dynamoi and approve the request once. That approval covers every tool in the app.

3. Ask an account-specific question Ask ChatGPT to list artists, check campaign status, summarize analytics, check distribution eligibility, or create a free Smart Link.

ChatGPT gets the directory catalog, which has no campaign launch, budget, billing, or Shop checkout tools. For those, use the Dynamoi dashboard.

Claude on the web or desktop

Open Settings → Connectors, choose Add custom connector, enter https://dynamoi.com/mcp, and sign in to Dynamoi when prompted.

Claude Code

Add the server, then run /mcp in Claude Code to sign in:

claude mcp add --transport http dynamoi https://dynamoi.com/mcp

The Dynamoi plugin from the agent plugins repository bundles Dynamoi skills with the directory catalog on https://dynamoi.com/mcp/directory:

/plugin marketplace add getDynamoi/agent-plugins
/plugin install dynamoi@dynamoi

Claude Code signs in with Claude's published identity, so it gets the same access as Claude on the web.

Cursor

Add Dynamoi to ~/.cursor/mcp.json, or .cursor/mcp.json in a project, then sign in when Cursor opens the browser:

{
  "mcpServers": {
    "dynamoi": {
      "url": "https://dynamoi.com/mcp"
    }
  }
}

VS Code

Add Dynamoi to .vscode/mcp.json:

{
  "servers": {
    "dynamoi": {
      "type": "http",
      "url": "https://dynamoi.com/mcp"
    }
  }
}

Codex CLI

codex mcp add dynamoi --url https://dynamoi.com/mcp
codex mcp login dynamoi

Or add the server to ~/.codex/config.toml and then run codex mcp login dynamoi:

[mcp_servers.dynamoi]
url = "https://dynamoi.com/mcp"

Codex CLI signs in with its published chatgpt.com identity, so it gets full access.

Gemini CLI

Install the Dynamoi extension from the agent plugins repository:

gemini extensions install https://github.com/getDynamoi/agent-plugins

OpenClaw

Add Dynamoi with Dynamoi's reviewed OpenClaw client document, then sign in:

openclaw mcp add dynamoi --url https://dynamoi.com/mcp --transport streamable-http --auth oauth \
  --oauth-client-metadata-url https://dynamoi.com/api/oauth/clients/openclaw \
  --oauth-scope "offline_access dynamoi:read dynamoi:mcp.full dynamoi:billing.read dynamoi:campaign.launch dynamoi:campaign.write dynamoi:distribution.apply dynamoi:distribution.read dynamoi:platform.read dynamoi:platform.write dynamoi:smart_links.write"
openclaw mcp login dynamoi

OpenClaw gets full access with or without the metadata URL, because it signs in on your own computer. The URL lets Dynamoi recognize it by its published identity.

Dynamoi skill on ClawHub

The Dynamoi skill on ClawHub teaches OpenClaw agents Dynamoi's workflows and safety rules. Install it with:

openclaw skills install @getdynamoi/dynamoi

Other MCP clients

Use https://dynamoi.com/mcp as a remote Streamable HTTP server. The client must handle the OAuth 401 challenge described in the MCP server overview. Clients that only support local stdio servers need a remote-to-stdio bridge. Headless agents can sign in with a device code. A client that signs in on your own computer gets full access; any other unreviewed client gets the directory tool set.

Related docs

• Dynamoi MCP Server
• Client permissions
• Connected Apps