Connect your agent over MCP
Point any MCP-capable agent at mcp.benchy.studio, mint a personal access token, and understand scopes, token exchange, and the audit log.
The hosted MCP server
Benchy runs one hosted Model Context Protocol server for your account: https://mcp.benchy.studio/api/mcp. You do not download the Benchy application, clone its source, run a local server, or configure its cloud infrastructure.
The tools available through that connection cover the Benchy products your account can access:
| Prefix | What your agent can work with |
|---|---|
bio_* | Profiles, bento blocks, drafts, styling, media, and quality audits |
canvas_* | Studio canvases, assets, nodes, and connectors |
world_* | 3D model uploads, releases, metadata, and categories |
shop_* | Seller onboarding, products, orders, refunds, and subscriptions |
box_* | Benchy Box packets, files, inventory, and comparisons |
writer_* | Documents and highlights |
skills_* and memories_* | The account knowledge available to your agents |
Choose a connection
Sign in to Benchy Studio → Profile → API keys, then open Connect a client. Select the agent or MCP host you use and follow that entry exactly.
There is deliberately no universal JSON block. Claude Code, Claude, ChatGPT, Codex, Cursor, VS Code, and other clients use different file formats and authentication methods. The in-product instructions give each client the right setup.
API keys
Use an API key when your client supports a configured bearer credential. Choose Read-only when the agent only needs to inspect your account, or Full access when it must make approved changes. New keys default to Read-only.
- Create a separate key for each agent or integration so you can revoke it independently.
- Choose an expiry and, when relevant, a monthly Benchys spending limit.
- Copy the key when Benchy shows it, then store it only where the selected client's instructions say. Never paste it into an ordinary chat message or document.
Hosted OAuth
Claude's hosted connectors, ChatGPT connectors, and other OAuth-capable MCP hosts can connect without an API key. Add https://mcp.benchy.studio/api/mcp as the remote MCP server. Your client opens Benchy in the browser so you can sign in and approve Read or Write access.
Use this browser authorization flow when the client offers it. The client holds the resulting connection; you do not copy a token between products.
Verify the connection
- Confirm the client shows benchy as connected.
- Ask the agent to discover its Benchy tools, resources, and prompts.
- Start with a read, such as listing your Bio sites or reading an existing record, before asking it to make a change.
- If a write returns
insufficient_scope, re-authorize with Write access. Do not ask the agent to bypass the permission.
Teach your agent
Benchy agent skills are optional Markdown instruction files that teach reliable workflows and safety rules. Downloading a skill gives your agent instructions; it does not install Benchy or move any Benchy infrastructure onto your computer. The hosted MCP connection remains the only product connection it needs.
Use ← and → to move between pages.