Loading…
Integrations
3DLogo.io is a browser-based 3D logo maker, and it ships an MCP server. Connect that server to ChatGPT, Claude, Grok, Claude Code, Cursor, VS Code, Gemini CLI or any other Model Context Protocol client and ask for a 3D logo, a coin, or a 3D model. The assistant hands you a link into the studio, keeps projects in your account, and can run Generate on your credits.
This one. Catalogues, example looks, studio links and logo images work at once; the first account tool (projects, previews, share links, Generate) asks you to sign in, then carries on.
https://3dlogo.io/api/mcpThe no-account subset on its own, for hosts that cannot sign in.
https://3dlogo.io/api/mcp/publicSettings → Connectors → Create (Developer mode must be on) → paste the signed-in URL and choose OAuth. ChatGPT registers itself, sends you here to sign in and approve, and the tools appear in the composer. Company-knowledge search uses the search and fetch tools.
Settings → Connectors → Add custom connector → paste the signed-in URL. Claude discovers the OAuth server, opens the sign-in and consent pages, and connects. Streamable HTTP, PKCE, dynamic client registration; the callback https://claude.ai/api/mcp/auth_callback is accepted.
grok.com → Connectors → New connector → Custom → paste the URL. Through the xAI API, pass it as a remote MCP tool (server_url, server_label: "3dlogo").
claude mcp add --transport http 3dlogo https://3dlogo.io/api/mcp
# or the plugin, which also installs the 3dlogo skill
/plugin marketplace add cottom/3dlogo.io
/plugin install 3dlogo@3dlogo{
"mcpServers": {
"3dlogo": { "type": "http", "url": "https://3dlogo.io/api/mcp" }
}
}VS Code: Command Palette → "MCP: Add Server" → HTTP. Cursor: Settings → MCP → Add. Gemini CLI: gemini mcp add --transport http 3dlogo https://3dlogo.io/api/mcp. Codex: codex mcp add 3dlogo --url https://3dlogo.io/api/mcp.
n8n, Make, Dify, the Claude Messages API connector, the OpenAI Responses API and the Gemini API all call a remote MCP server without a browser, so they cannot complete OAuth. Create a connector token in Account (Connected apps → Connector tokens), choose its scopes and expiry, and send it as a bearer header. It acts as you, within those scopes, and you can revoke it any time.
Authorization: Bearer 3dl_pat_… → https://3dlogo.io/api/mcpn8n: MCP Client node → Credential type “Bearer”. Claude Messages API: mcp_servers[].authorization_token. OpenAI Responses API: tools[].authorization. Gemini: headers.
| Tools | Needs | Does |
|---|---|---|
| build_logo_editor_link | Nothing | A link that opens the editor with a wordmark typed (or your logo image loaded), a material, lighting and motion set. |
| build_coin_studio_link | Nothing | Same for the coin studio: text, look, colours, blank edge. |
| browse_looks | Nothing | The example looks with a rendered image each, what they suit, and a link that applies one. |
| upload_logo_image, request_logo_image_upload | Nothing | Hand over an existing logo file (attached in chat, by URL, or uploaded from a coding agent) and get it back styled in 3D. |
| list_materials, list_coin_looks, get_plans | Nothing | The catalogues and what Free, Pro and Ultra include. |
| list_projects, get_project, search, fetch | Account | Read saved logos, coins and meshes with their links. |
| get_project_preview, get_generation_preview | Account | A picture of a saved design or a generated mesh, as an hour-long signed image URL. |
| create_text_logo_project, create_image_logo_project | Account | Save a wordmark or an uploaded logo as a project. |
| update_project, duplicate_project | Account | Rename, publish, or restyle a saved project without opening the studio; copy one for a variant. |
| create_share_link, list_share_links, revoke_share_link | Account | A share page, the iframe embed snippet, oEmbed and a poster image; unlisted by default. |
| create_invite_link | Account | Invite an editor or viewer to a project. |
| quote_generation, generate_3d_model, get_generation_status | Account | Run Generate on credits and poll it. |
| save_generation_as_project | Account | Keep a finished mesh; publish it for a share page and a GLB URL. |
| delete_project | Account | Permanent; assistants are told to confirm first. |
A skill in the open Agent Skills format teaches an assistant when and how to use the server: which endpoint, which tool for which ask, the credit and plan rules. SKILL.md and the tool reference.
Writing about the connector, or made something with the studio? A link back helps others find it. Use a plain link, or the badge:
<a href="https://3dlogo.io">3DLogo.io - free 3D logo maker</a><a href="https://3dlogo.io"><img src="https://3dlogo.io/badges/made-with-3dlogo.svg" alt="Made with 3DLogo.io" width="176" height="32" /></a>[](https://3dlogo.io)The MCP server is listed in the official MCP registry as io.github.cottom/3dlogo, on Smithery, and on Glama. A machine-readable card lives at /.well-known/mcp/server-card.json.
Yes. 3DLogo.io runs an MCP server, so any assistant that speaks MCP can drive it: ChatGPT, Claude, Claude Code, Cursor, VS Code, and Grok. The assistant can list materials and coin looks, build a styled editor link from a wordmark or an uploaded logo image, and read plan information. Signed-in connections can also save projects, publish share links, and run Generate.
No. Connect /api/mcp and the catalogue, example-look, studio-link and logo-image tools work at once; the first time the assistant calls an account tool (projects, previews, share links, Generate) it asks you to sign in and approve the connection, then continues. /api/mcp/public is the same no-account subset for hosts that cannot do OAuth.
The MCP server is the programmatic surface, and it is a real one: it is what the assistants call. There is no separate REST API. If you are building an integration rather than connecting an assistant, MCP is the interface to target.
Yes. Create a share link for a design, then use the embed snippet, which is an iframe pointing at the share token plus a credit line. oEmbed is supported, so platforms that resolve oEmbed can unfurl a share link on their own.
Only on a signed-in connection. The OAuth endpoint exposes projects, publishing, invites, and Generate, and a Generate run spends that account’s own credits, so it is your allowance being used and it shows in your history. The no-account endpoint cannot reach any of that.
The OAuth flow asks for consent every time rather than assuming it: a client that omits the consent prompt is redirected so the prompt is shown anyway. The consent screen lists three connector scopes, logo:read, logo:write and generate, and a connection is held to whichever it was granted. You are approving one assistant to act on your account, and you can disconnect it from Account at any time.
Yes. Those hosts cannot complete an OAuth sign-in, so Account has connector tokens: a bearer token with the scopes and expiry you choose, shown once, revocable any time. Send it in the Authorization header to /api/mcp and the account tools work as you.
Yes. Once a project has been opened and saved, get_project_preview returns a signed image URL of its last render, and create_share_link returns the share page, the iframe embed snippet, the oEmbed endpoint and a poster image. Whether the picture appears inline depends on the host; the URL always works.
Anything that speaks MCP over Streamable HTTP. ChatGPT, Claude, Claude Code, Cursor, VS Code, and Grok are the ones with setup steps above; others work the same way if they accept a server URL.
No. Export a transparent PNG from the editor and place it in Figma. For a design that will change, an embed or a share link keeps a single source; a pasted PNG does not.