Studio MCP
Studio MCP exposes one Studio bot to MCP-compatible clients. It is useful when a human operator or external client wants to call a specific bot's tools, ask that bot questions, or route trading commands through that bot's context.
Studio MCP vs Hub MCP
| Studio MCP | Hub MCP |
|---|---|
| Belongs to a Studio bot. | Belongs to a 24/7 Web3 agent. |
| Managed from the bot cockpit MCP tab. | Managed from Hub → Agents & Keys / agent detail. |
| Uses bot-scoped keys and bot context. | Uses agent identity, funding, scopes, and operational logs. |
| Best for operator workflows around one bot. | Best for always-on agent runtime operations. |
If you are configuring a community bot, website widget, or personal trading bot, use Studio MCP. If you are onboarding a continuously running agent, use Hub.
What the MCP tab contains
The Studio bot MCP tab can include:
- API keys.
- Visible tools for the current scope.
- Agent card preview or publishing controls.
- Operation logs.
Keys are revealed once at creation time. Store them in a secrets manager or local MCP client configuration and rotate them if exposed.
Scopes
MCP keys use the same scope hierarchy:
| Scope | Use it for |
|---|---|
read | Monitoring, portfolio reads, logs, market/research lookups. |
trade | Trading commands and mutable trade workflows allowed by policy. |
manage | Sensitive configuration and key-management actions. |
Use the minimum scope that works. A monitoring client should not receive a trade key. A trade automation should not receive manage scope unless it truly needs configuration control.
Tool discovery
Do not rely on a hardcoded tool count. The visible tools depend on runtime registry state, environment configuration, key scope, and principal context.
Use MCP tools/list with the current key to see the exact tools available.
Safe setup pattern
- Open the bot cockpit.
- Go to MCP.
- Create a key with the minimum scope.
- Copy the secret immediately.
- Add it to the MCP-compatible client.
- Call
tools/listto verify visible tools. - Test a read-only call before enabling trade actions.
- Rotate or revoke the key when the integration changes.
Common issues
My MCP client connects but cannot call a trade tool.
The key may be read scoped, or the bot's risk policy may block the action.
I lost the key secret. Revoke the old key and create a new one. Full secrets are shown only once.
I created a key in Hub but expected it to control a Studio bot. Hub keys are agent-level. Create bot-scoped keys from the Studio bot MCP tab.