capabilities.work

Provision an MCP Server

A 4-step recipe with Composio. We can help you get access.

Recipe · 4 steps

Provision an MCP Server

with Composio

Create an auth config, an MCP server, and a per-user MCP instance.

  1. Create an auth config for the toolkit so the MCP server has an authentication configuration to reference.
  2. Create an MCP server that references the new auth config and restricts the tools it exposes.
  3. Read the MCP server back to capture its authoritative MCP URL and client install commands.
  4. Create a per-user instance of the MCP server so the end user gets their own connection-scoped endpoint.
What you'll need to have ready
  • apiKey: Composio project API key sent in the x-api-key header.
  • toolkitSlug: The toolkit slug the MCP server exposes (e.g. "linear").
  • authType: The auth config type discriminator (e.g. "use_composio_managed_auth").
  • serverName: A name for the new MCP server.
  • allowedTools: Optional list of tool slugs the MCP server is allowed to expose.
  • userId: The end-user identifier the MCP server instance is created for.
For your developer

Arazzo workflow composio:provision-mcp-server, 4 operations: postAuthConfigs → postMcpServers → getMcpById → postMcpServersByServerIdInstances. Specs on APIs.io.

More recipes with Composio

Connect an Account via a New Auth ConfigDisable an Active TriggerDiscover and Execute a ToolExecute a Tool on a User's Connected AccountGenerate a Hosted Auth LinkNatural Language Tool ExecutionRefresh a Connected AccountSet Up a TriggerTool Router Connect a ToolkitTool Router Session