Dynamoi MCP Server

Music marketing for AI agents.

The Dynamoi MCP server connects ChatGPT, Claude, Cursor, and other AI agents to Dynamoi, the music marketing platform for artists, labels, and managers. Agents can create free Spotify Smart Links, run managed YouTube and Meta promotion campaigns, read campaign and Smart Link analytics, check platform status, and apply for music distribution. Use the hosted MCP server, or use this package as a library.

https://dynamoi.com/mcp

The hosted server needs no install. Point any MCP client that supports remote Streamable HTTP and OAuth at that URL, and the user signs in with their Dynamoi account.

About Dynamoi

Dynamoi is a music marketing platform founded in 2021 by Trevor Loucks. It runs managed Meta and YouTube ad campaigns, music distribution, and royalty analytics for independent artists, labels, managers, and YouTube creators, alongside free Smart Links and analytics.

• Free Smart Links: release pages and artist hubs built from Spotify URLs, with link analytics, themes, validated pixel IDs, and team seats.
• Managed Smart Campaigns: Meta ads that promote Spotify tracks, albums, and playlists.
• YouTube campaigns: managed Google Ads campaigns for YouTube channel growth.
• Music distribution: opt-in delivery to 100+ stores. Applications are scored against five requirements, and approval is not guaranteed.
• YouTube promotion Shop: one-off YouTube video promotion with no subscription.

Campaigns run on Dynamoi's own managed Meta and Google ad infrastructure. They reach real people through official ad networks, never bots, fake streams, or paid playlist placement. Results vary and are never guaranteed.

Dynamoi is based in Sioux Falls, South Dakota, and is operated by humans, assisted by AI. People make the decisions and are accountable for every campaign and support reply. AI helps with ad creative, campaign monitoring, reporting, and routine tasks.

Smart Links are free. Starter is $25/month with a $50 launch campaign credit, and campaign budgets start at $10/day. See pricing.

Agents can read the same overview before sign-in through the dynamoi_about tool or the dynamoi://about resource.

Connect

Each client opens the Dynamoi sign-in page on first use.

ChatGPT

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

Claude (web and desktop)

Open Settings → Connectors, choose Add custom connector, and enter https://dynamoi.com/mcp.

Claude Code

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

Then run /mcp in Claude Code to sign in.

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

Cursor

Use the Add to Cursor badge above, or add Dynamoi to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

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

VS Code

Use the Install in VS Code badge above, or add Dynamoi to .vscode/mcp.json:

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

Gemini CLI

Install the Dynamoi extension from the agent plugins repository:

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

Codex CLI

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

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

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

Other MCP clients

Use https://dynamoi.com/mcp as a remote Streamable HTTP server. The client must handle an OAuth 401 challenge (MCP authorization). Stdio-only clients need a remote-to-stdio bridge.

Which tools a client sees

The server has two tool catalogs. It picks one from the OAuth client that signed in, not from anything the client claims about itself.

Signing in does not skip permission checks. Every tool call still needs its OAuth scopes, and the user's role must allow access to the artist, campaign, or Smart Link.

Tools

"Reads" tools are marked read-only. "Changes data" tools write to Dynamoi or start an action with an outside provider.

Full tool descriptions and input schemas come from tools/list, or from getDynamoiToolDefinitions() in this package.

The full-only Studio tools (dynamoi_update_smart_link_release_settings and dynamoi_update_smart_link_artist_hub_settings) are not part of the approved directory contract and are never listed in the directory profile.

Previously approved directory clients may continue calling the exact dynamoi_update_smart_link name with its approved schema. New directory tool lists omit that compatibility handler and advertise the two single-purpose operations above. Compatibility calls keep the same Smart Link write scope, confirmation, account, and domain checks.

Money and safety

• Smart Links are free. Creating or updating them never charges anyone.
• Launches and budget changes are real. dynamoi_launch_campaign and dynamoi_update_campaign go through the same backend checks as the Dynamoi web and mobile apps: permissions, promo limits, and repeat-request protection. Whether a person approves each call is up to the MCP client's tool-approval settings, so keep approval on for tools that change data.
• Daily budgets need the user's funding consent. A DAILY budget is funded one 24-hour window at a time. Available credits and campaign funds are used first, then the card the user saved in Dynamoi is charged automatically. The agent must show the user the exact consent text, then send authorizeAutomaticDailyFunding: true with the matching acceptedConsentVersion and acceptedConsentCopyHash. This applies to launches, budget updates, and resumes that need card funding. Without consent the request is refused. The consent values are exported from @dynamoi/mcp/consent.
• Total budgets use existing credit and need no funding consent.
• Agents never handle payment credentials. Subscriptions, plans, and billing setup happen only in the Dynamoi dashboard, where subscriptions start through hosted Stripe Checkout. No tool starts a subscription.
• Shop checkout is only a link. dynamoi_shop_create_checkout creates an unpaid Stripe Checkout Session. The user pays on Stripe, and no order exists until the payment is verified.
• Distribution applications start a manual review. Submitting one does not approve distribution, accept an agreement, or deliver music to stores.
• The directory catalog exposes no tools that spend money, start a subscription, or create a checkout.

Authentication

Dynamoi uses OAuth 2.1 through its authorization server at https://dynamoi.com/api/auth. Clients find it through the server's metadata:

• Protected resource: https://dynamoi.com/.well-known/oauth-protected-resource/mcp
• Authorization server: https://dynamoi.com/.well-known/oauth-authorization-server

Without a token, a request gets a 401 with a WWW-Authenticate challenge. That challenge asks for every scope the client's catalog uses, so one consent covers the whole catalog. A full-catalog client that signed in with fewer scopes is asked once for the rest.

Protocol support

• MCP 2026-07-28: stateless requests with per-request _meta, including server/discover.
• MCP 2025-11-25 and earlier initialize-based revisions, for clients that have not moved to 2026-07-28.
• Streamable HTTP, POST only. Responses are JSON, or SSE for 2025-era clients that accept it. The server keeps no sessions and opens no standalone stream, so GET and DELETE return 405.

Using the package

Most people should connect to the hosted server. Install the package if you are building against the Dynamoi MCP contract: tool definitions, Zod schemas, result types, OAuth scope maps, or the stateless HTTP handler.

npm install @dynamoi/mcp

The package is ESM-only and built on MCP TypeScript SDK v2 (@modelcontextprotocol/server).

A host provides a Phase3Adapter, which connects each tool to its own services. It also verifies the caller before it serves a request:

import {
  createDynamoiMcpServer,
  handleMcpHttpRequest,
  type DynamoiMcpToolProfile,
  type Phase3Adapter,
} from "@dynamoi/mcp";

export async function handleMcp(
  request: Request,
  adapter: Phase3Adapter,
  toolProfile: DynamoiMcpToolProfile,
): Promise<Response> {
  // Authenticate the request and check scopes first; this package does not
  // verify tokens. The profile defaults to "directory" if you omit it.
  const parsedBody = request.method === "POST" ? await request.json() : null;
  return handleMcpHttpRequest({
    request,
    parsedBody,
    createServer: () => createDynamoiMcpServer({ adapter, toolProfile }),
  });
}

createDynamoiMcpServer also accepts authorizeToolCall (answer a call before it runs, for example with a step-up challenge), onToolCall (a telemetry hook), and oauthScopes.

Every request builds a new server. handleMcpHttpRequest sends 2026-07-28 requests to the SDK's stateless handler and 2025-era requests to a stateless per-request transport.

Links

MIT licensed. See LICENSE.

Artist workspace

dynamoi_open_workspace({}) returns an authorized artist roster and declares a read-only MCP Apps resource with global and thread entrypoints. On supported hosts, browse campaigns and Smart Links, inspect reported metrics, and deliberately share the selected record and artist references with the next conversation turn. Channel observations retain their own window, provenance and coverage; they are not attributed to the campaign. No pricing, checkout or campaign-write controls appear in this workspace. Unsupported hosts retain the ordinary text and tool result.

The existing Smart Link theme preview remains separate. Composer mentions, settings, file viewers and events are not advertised. Local App/AppBridge fixtures establish their tested contract only; actual ChatGPT host support and public approval require separate evidence.

The browser bridge is bundled locally with the compatible MCP Apps v2 SDK; no CDN is needed. bun scripts/build-workspace.cjs regenerates the checked-in source bundle and bun scripts/build-workspace.cjs --check verifies reproducibility from the package directory. The ordinary package build runs the same owner. Keep the generated script synchronized with its browser/view/data sources.