Developers
StableUser
Claude
Use Blocchi as a custom remote connector in Claude.
Before you begin
A Blocchi account with appropriate data access is required. Claude custom connectors may require organization-admin setup on Team / Enterprise plans. The interface and entitlements can change.
Setup on Claude web or desktop
- In Claude on web or desktop, find the place where custom connectors (remote MCP servers) are added. Menu names vary by version and plan; follow Claude's official guide linked below for the current path.
- Enter Blocchi as the name and
https://www.blocchi.ai/api/mcpas the remote MCP URL. - Review authentication. If Claude offers an OAuth sign-in and recognizes Blocchi's authorization metadata, follow the sign-in and permission review. Blocchi must accept the OAuth client identity Claude presents; this has not been certified for every client.
- If OAuth cannot finish, stop: do not paste a Blocchi key into a conversation or an organization-wide shared configuration. Use a credential field only if your Claude version documents one for custom connectors, and keep any secret private and scoped.
- Add and enable the connector, then enable Blocchi in a new conversation if your client requires it.
- Ask: “List the Blocchi tools available to me and summarize their permissions. Do not execute writes.”
Test and troubleshoot
A connection can be healthy while sources are not synchronized. Check real data readiness in Blocchi before interpreting metrics. If Claude reports an unknown OAuth client or rejected redirect, do not weaken authorization: use a credential flow your client documents or wait for an administrator to configure a certified OAuth client.
Claude's official remote MCP connector guide describes current menus and plan rules.
Last updated on