MCP Server

Give AI tools direct access to the Motomarks brand library. The hosted Model Context Protocol server lets Claude, Cursor, VS Code, and any MCP-compatible client search brands, read brand data, and build logo CDN URLs.

Endpoint

One hosted endpoint, streamable HTTP transport. Sign-in happens in your browser via OAuth the first time a client connects — no keys to copy.

MCP endpoint

https://motomarks.io/api/mcp

Setup

Add the endpoint to your client. On first use it opens a browser window to sign in to your Motomarks account and authorize access. Cursor and VS Code users can install in Cursor or install in VS Code with one click.

Claude Code

claude mcp add --transport http motomarks https://motomarks.io/api/mcp

Cursor · ~/.cursor/mcp.json

{
  "mcpServers": {
    "motomarks": {
      "url": "https://motomarks.io/api/mcp"
    }
  }
}

VS Code (GitHub Copilot) · mcp.json

{
  "servers": {
    "motomarks": {
      "type": "http",
      "url": "https://motomarks.io/api/mcp"
    }
  }
}

stdio-only clients (Claude Desktop, custom)

{
  "mcpServers": {
    "motomarks": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://motomarks.io/api/mcp"]
    }
  }
}

Authentication

The server implements the MCP authorization spec: OAuth 2.1 with dynamic client registration and PKCE. Your client registers itself, you sign in once in the browser, and tokens refresh automatically.

Requests count toward your plan's daily rate limits; free-plan attribution requirements apply.
CDN image URLs returned by tools are signed with your publishable key. If your account has no API key yet, one named "MCP" is created automatically.
Revoke access anytime by revoking the API key in your dashboard.

Headless authentication

For CI, servers, or clients that cannot open a browser, authenticate with a secret API key from your dashboard instead of OAuth.

Remote (Bearer header)

Authorization: Bearer YOUR_SECRET_KEY

Local proxy

npx -y mcp-remote https://motomarks.io/api/mcp --header "Authorization: Bearer YOUR_SECRET_KEY"

Tools

All tools are read-only and scoped to your account's plan and rate limits.

search_brands — search published brands by name, company, or slug; optionally include ready-to-use CDN image URLs.
get_brand — full brand detail: description, colors, palette, social links, company facts, and FAQs.
list_brand_assets — available logo assets with type, format, size, aspect, dimensions, and CDN URLs.
build_image_url — deterministic image CDN URL authenticated with your publishable key.
describe_api_endpoint — HTTP reference for the raw REST API.
get_account — your plan, attribution status, and today's usage against the daily limit.

The server also exposes resources (motomarks://docs/image-cdn, motomarks://docs/api-v1, motomarks://brand/{slug}) and prompts (find_brand_logo, embed_brand_image) for clients that support them.

Example prompts

Things to ask once the server is connected.

"Add the BMW badge logo to this pricing table."
"What are Lamborghini's brand colors? Give me the full palette."
"List every Toyota wordmark and pick the best one for a dark navbar."
"How many API requests do I have left today?"

Registry manifests, client plugin files, and agent skills live in the motomarks/motomarks-mcp repository (MCP Registry name io.motomarks/mcp).