this is a quick faq/guidance doc about how we are thinking about user’s building on top of composio mcp.

<aside> 👉

our MCP servers are still an experimental product - we don’t recommend customer building on top of it but rather using our much more stable sdk/api offering https://docs.composio.dev/resources/model-context-protocol

</aside>

Currently we are not envision our fully managed MCP servers to function like a devtool and something you build on top of but rather for provider who have MCP as a way to quickly integrate with our tools.

We think the protocol is promising but we suggest customers intending to build on top of us use our https://docs.composio.dev/getting-started/welcome sdk/api offerings for maximum control, flexibility and reliability - we do not expect to be supporting customers in the short-term building on top of our MCP service


What is pricing like for Composio MCP?

How are you guys thinking about custom MCP clients?

How does auth work?