Dynamoi MCP Server

Dynamoi MCP Server

Music promotion, built for AI agents.

Music promotion from your AI agent. Connect Claude, ChatGPT, Codex or Cursorto check results and manage Smart Links and, where your assistant allowspurchases, launch and fund Spotify and YouTube campaigns with the artist'sexplicit consent. Artists who distribute with Dynamoi can manage releases theretoo. 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 remoteStreamable HTTP and OAuth at that URL, and the user signs in with theirDynamoi account.

About Dynamoi

Dynamoi is a music promotion platform founded in 2021 by Trevor Loucks. Itruns managed Meta and YouTube ad campaigns for independent artists, labels,managers, and YouTube creators on any distributor, alongside free Smart Linksand analytics. Artists who want everything in one account can also distributethrough Dynamoi.

• Free Smart Links: release pages and artist hubs built from SpotifyURLs, 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 channelgrowth.
• Music distribution (optional): delivery to 100+ stores. Applications arescored against five requirements, and approval is not guaranteed.
• YouTube promotion Shop: one-off YouTube video promotion with nosubscription.

Campaigns run on Dynamoi's own managed Meta and Google ad infrastructure. Theyreach real people through official ad networks, never bots, fake streams, orpaid 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 everycampaign and support reply. AI helps with ad creative, campaign monitoring,reporting, and routine tasks.

Smart Links are free. Starter is $25/month per artist, and your planprice becomes ad credit. Eligible new artists get double credit the first month.Campaign budgets start at $10/day. Seepricing.

Agents can read the same overview before sign-in through the dynamoi_abouttool 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 URLhttps://dynamoi.com/mcp and OAuth authentication. ChatGPT gets thedirectory catalog.

Claude (web and desktop)

Open Settings → Connectors, choose Add custom connector, and enterhttps://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 theagent plugins repositorybundles Dynamoi skills with the directory catalog onhttps://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 theagent 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"

OpenClaw

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

The metadata URL is Dynamoi's reviewed client document for OpenClaw, whichrecognizes OpenClaw by its published identity. OpenClaw gets Full access withor without it, because it signs in on your own computer.

The dynamoi skill teaches OpenClaw agents theDynamoi workflows and safety rules. Install it from ClawHub withopenclaw skills install @getdynamoi/dynamoi.

Command line

The dynamoi CLI signs in once with OAuth and runs anyDynamoi tool as a command, generated from the live tool schemas:

npm install --global dynamoi
dynamoi login
dynamoi tools

Other MCP clients

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

Which tools a client sees

Every client gets one of two tiers. The server picks it from the identity theOAuth client signs in with, not from anything the client claims about itself.

Seeing a tool is not permission to call it. A Full client can approve everyscope for its tools; a Directory client is never granted the scopes that Fulltools need, so those calls are refused.

Signing in does not skip permission checks. Every tool call still needs itsOAuth 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 orstart an action with an outside provider.

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

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

Previously approved directory clients may continue calling the exactdynamoi_update_smart_link name with its approved schema. New directory toollists omit that compatibility handler and advertise the two single-purposeoperations 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 anddynamoi_update_campaign go through the same backend checks as the Dynamoiweb and mobile apps: permissions, promo limits, and repeat-requestprotection. Whether a person approves each call is up to the MCP client'stool-approval settings, so keep approval on for tools that change data.
• Every budget needs the user's funding consent. A DAILY or TOTALbudget is funded one window at a time: available credits and campaign fundsfirst, then the card the user saved in Dynamoi is charged automatically (aTOTAL budget never beyond its total). The agent must show the user the exactconsent text for the budget type, then send, for DAILY,authorizeAutomaticDailyFunding: true with acceptedConsentVersion andacceptedConsentCopyHash, or, for TOTAL, acceptedTotalConsentVersion andacceptedTotalConsentCopyHash. This applies tolaunches, budget updates, and resumes that need card funding. A DAILYbudget refuses the TOTAL consent and the reverse; without consent therequest is refused and never charged. The consent values are exported from@dynamoi/mcp/consent.
• Agents never handle payment credentials. Subscriptions, plans, andbilling setup happen only in the Dynamoi dashboard,where subscriptions start through hosted Stripe Checkout. No tool starts asubscription.
• Shop checkout is only a link. dynamoi_shop_create_checkout creates anunpaid Stripe Checkout Session. The user pays on Stripe, and no order existsuntil the payment is verified.
• Distribution applications start a manual review. Submitting one does notapprove distribution, accept an agreement, or deliver music to stores.
• The directory catalog exposes no tools that spend money, start asubscription, or create a checkout.

Authentication

Dynamoi uses OAuth 2.1 through its authorization server athttps://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 consentcovers the whole catalog. A full-catalog client that signed in with fewerscopes is asked once for the rest.

Protocol support

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

Using the package

Most people should connect to the hosted server. Install the package if youare 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 ownservices. 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 callbefore it runs, for example with a step-up challenge), onToolCall (atelemetry hook), and oauthScopes.

Every request builds a new server. handleMcpHttpRequest sends 2026-07-28requests to the SDK's stateless handler and 2025-era requests to a statelessper-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.