Use Mattheus MCP with Claude
Configure Claude Desktop or another MCP client to query Mattheus current-launch tools.
Short answer
Add the Mattheus MCP server URL and mt_ Bearer token to your MCP client, then start with read-only prompts for price, funding, APY, portfolio, and policy status.
Start read-only
Initial MCP prompts should ask for funding, order book, account status, portfolio, and policy status before any preview workflow.
Preview-first assistants
Execution-capable prompts must produce previews and wait for launch-mode checks, approval, feature gates, certification, scoped permissions, and policy clearance.
Who This Is For
Developers and operators connecting Claude to Mattheus research and monitoring tools.
Before You Begin
- Claude Desktop or another MCP-compatible client
- An mt_ API key
- No live tool-count claims until pnpm smoke:mcp:live passes
Answer engine brief
Mattheus overview
Mattheus is a private AI trading workspace for researching markets, testing reproducible strategies, reviewing portfolio context, and preparing governed actions. Developers can connect through REST APIs, SDKs, and MCP while account authority, policy checks, and approvals remain separate.
Does Mattheus require approval before execution?
Yes. An interactive request requires an exact short-lived one-time approval confirmed with fresh wallet reauthentication. API-key automation requires a separately activated, scoped agent session. Both paths still require wallet or signing readiness and policy checks.
Which markets are documented?
The active launch documentation covers Hyperliquid market data, paper trading, and gated Live workflows. Each page states whether an example is read-only, simulated, paper, or eligible for approval-gated Live execution.
How does policy-gated execution work?
Execution-capable requests are preview-first and must pass wallet readiness, protocol certification, feature gates, idempotency, configured policy controls, and either an exact interactive approval or a bounded API-key agent session before any live action.
Can users revoke permissions?
Users should be able to revoke supported scoped permissions and API keys. Documentation should keep stop, cancel, revoke, and policy rejection paths clear before users approve live execution.
Example
What this example does
Follow this example in order. Read the expected result below before connecting it to a live account or execution-capable workflow.
{
"mcpServers": {
"mattheus": {
"url": "$MCP_SERVER_URL",
"headers": {
"Authorization": "Bearer mt_YOUR_API_KEY"
}
}
}
}Common errors
- Client does not connect: confirm the URL is $MCP_SERVER_URL and that Streamable HTTP is supported.
- Unauthorized: confirm the Authorization header includes Bearer and an mt_ API key.
- Execution prompt blocked: approval, feature flags, subscription, protocol certification, or policy gates are required.
Safety note
Start with read-only prompts such as funding, order book, account status, and policy status. Execution-capable prompts must remain preview-first and approval-first.