Motomarks MCP

MCP Registry:io.motomarks/mcp· Auth: OAuth 2.1 or API key · Hosting: Motomarks Cloud

The Motomarks MCP Server connects MCP-compatible clients to the Motomarks brand library. Once configured, your AI tools can search automotive brands, fetch brand data and color palettes, browse logo assets, and generate ready-to-embed CDN image URLs. Authentication usesOAuth 2.1(browser sign-in) or aMotomarks secret API key, so every request respects your plan and rate limits.

- Search and inspectany published car brand: names, slugs, descriptions, colors, palettes, social links, and company facts.
- Browse logo assetsper brand: full logos, badges, and wordmarks in webp, png, and svg across five sizes.
- Generate CDN image URLsauthenticated with your publishable key, ready to paste into HTML, React, or Markdown.
- Check your account: plan, attribution status, and today's API usage.

Transport: streamable HTTP. On first connection your client runs a browser-based OAuth flow (dynamic client registration + PKCE) against your Motomarks account. No JSON editing or manual token handling required.

For clients that only speak stdio, connect throughmcp-remote:

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

Requires Node.js 20+. The proxy opens a browser for OAuth sign-in and caches tokens locally.

For CI, backends, or non-interactive setups, authenticate with a Motomarkssecret API key(sk_..., created in yourdashboard) instead of OAuth by sending it as a Bearer token:

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

Resources:motomarks://docs/image-cdn,motomarks://docs/api-v1,motomarks://brand/{slug}. Prompts:find_brand_logo,embed_brand_image.

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

- All traffic is encrypted in transit over HTTPS.
- OAuth 2.1 (PKCE, dynamic client registration) or scoped API keys control access.
- Tools respect your Motomarks plan, attribution requirements, and rate limits.
- Secret keys are never echoed back by tools; account output masks them.

MCP clients can act on your behalf. Only use trusted clients, prefer least privilege, and review your connected apps in the Motomarks dashboard. SeeSECURITY.mdfor reporting.

This repo contains no server code — the server is hosted athttps://motomarks.io/api/mcp. Publishing means listing the endpoint in registries and directories:
- Verify themotomarks.iodomain for theio.motomarksregistry namespace (DNS or HTTP challenge), then publish the manifest:mcp-publisher login dns --domain motomarks.io && mcp-publisher publishwithserver.json.
- Submit the registry entry / repo to MCP directories (official MCP Registry, Cursor marketplace, Claude connectors, PulseMCP, Smithery, Glama).

- Docs:motomarks.io/docs/mcp
- Issues:GitHub issues
- Email:support@motomarks.io

Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB