Composio releases step‑by‑step Metabase MCP tutorials to make APIs agent‑readable
- Composio published Claude Code tutorials for Metabase and Composio integrations, showing on May 17 how to connect MCP servers through either Composio Connect or SDK. - The guides center on one MCP URL, OAuth-based authentication, and access to 20,000 tools across 1,000-plus apps, according to Composio’s documentation. - Developers can find the next setup step in Claude Code’s `/mcp` flow or Composio’s plugin install docs.
Composio has published a pair of step-by-step guides showing developers how to connect Metabase and Composio itself to Claude Code through the Model Context Protocol, or MCP. The documentation lays out two setup paths in each case: a direct route through Composio Connect and a programmatic route through the Composio SDK. Both pages include Python and TypeScript examples, according to Composio’s toolkit documentation. The release adds another set of vendor-authored playbooks to a fast-growing MCP ecosystem built around turning external services into callable tools for coding agents. ### What do the new guides actually walk a developer through? Composio’s Metabase page says the Claude Code integration can be set up in five steps, starting with generating an MCP URL, launching Claude Code, opening the `/mcp` menu and completing authentication through a Composio-hosted OAuth flow. The same page says developers can then expose Metabase actions such as running card queries, copying dashboards and triggering schema syncs as tools inside Claude Code. (composio.dev) The Composio-on-Composio guide follows the same structure. Composio says users can authenticate through the same MCP flow and then call higher-level management tools including connection setup, tool discovery, response-schema lookup and remote code or bash execution in a sandbox. ### Why are Metabase and Composio notable examples? Metabase is a business-intelligence system with dashboards, cards and datasets that are usually handled through a graphical interface or API. (composio.dev) Composio’s guide turns those functions into named tools with defined inputs and outputs that Claude Code can invoke from a terminal session, according to the documentation. Composio’s own toolkit page shows the same pattern applied to infrastructure for agent operations rather than a line-of-business app. (composio.dev) The listed tools include initiating connections, checking active connections, retrieving response schemas and executing multiple tools in parallel, which puts authentication and tool metadata inside the same callable surface area as the business action itself. (composio.dev) ### How does this fit into Claude Code’s MCP model? Anthropic says Claude Code can connect to external tools and data sources through MCP, which it describes as an open-source standard for AI-tool integrations. Claude Code’s documentation says remote HTTP servers are the recommended transport for cloud services and that connected servers can expose tools, prompts and resources directly into a session. (composio.dev) Anthropic introduced MCP on November 25, 2024, describing it as an open standard for linking AI assistants with repositories, business tools and development environments. The company said the protocol was designed to replace fragmented one-off integrations with a single connection model built around MCP servers and MCP clients. ### Where do authentication and tool contracts show up in practice? (code.claude.com) Composio’s pages put authentication near the top of the setup flow rather than treating it as a side task. The Metabase and Composio tutorials both tell users to authenticate through Composio after adding the MCP connection inside Claude Code, and Composio’s separate plugin documentation says its Claude Code plugin uses in-flow OAuth so users do not paste API keys into configuration. (anthropic.com) The Composio toolkit also exposes schema-oriented utilities as tools. Its documentation lists functions such as “Get response schema” and “Get required parameters for connection,” which makes the contract around a tool call visible to the agent at runtime rather than leaving it buried in external docs. ### What does a developer do next if they want to try it? Claude Code’s documentation says users can add remote MCP servers with the `claude mcp add --transport http` command, while Composio’s tutorials route users through a generated MCP URL and the in-product `/mcp` menu. (composio.dev) Composio also offers a plugin route that installs its MCP server and bundled skills through Claude Code’s marketplace commands. (composio.dev) Composio’s plugin docs say the package gives Claude Code access to the same Composio Connect MCP server and more than 1,000 apps, while the toolkit pages say the broader platform can load 20,000 tools across those apps on demand. For developers evaluating the new Metabase or Composio tutorials, the next concrete step is the same one named in the docs: add the server, authenticate, and inspect the available tools in Claude Code. (composio.dev) (code.claude.com)