Other MCP clients
Generic Streamable HTTP and Gemini CLI setup for Blocchi.
Generic remote MCP connection
Use https://www.blocchi.ai/api/mcp with transport Streamable HTTP. Blocchi supports ordinary MCP initialize, tools/list, and authorization discovery. The client's identity must resolve to an authorized Blocchi user or machine identity.
- Add a remote HTTP MCP server named Blocchi.
- Prefer OAuth authorization if your client supports the authorization metadata and an accepted client identity.
- Otherwise use a scoped key in a private client credential setting (Bearer authorization). Do not publish a token or paste it into the AI chat.
- Reconnect and check
tools/list. Test with a read-only query before requesting writes.
Gemini CLI
Gemini CLI supports HTTP MCP servers. The baseline server registration is:
This only registers the server. Authorization still must be configured: use the CLI's supported OAuth method when compatible, or securely supply a scoped Bearer credential in user-local configuration. Do not append a live token to shell history. Confirm the current CLI options and authentication behavior in the official Gemini CLI MCP guide.
When to use REST instead
Choose the REST API for durable backend integrations, ETL and scheduled jobs. MCP is the agent-facing discovery and orchestration adapter; they share the same governed application services.
Last updated on