---
canonical_url: "https://docs.composio.dev/docs/apps-and-toolkits/provider-mcps"
markdown_url: "https://docs.composio.dev/docs/apps-and-toolkits/provider-mcps.md"
product: "platform"
version: null
last_updated: null
---

# What are Provider MCPs (/docs/apps-and-toolkits/provider-mcps)

A **Provider MCP** toolkit connects to an MCP server that the product's own team hosts and maintains. Composio acts as the MCP client, syncs the tools that server publishes, and wraps them as an ordinary toolkit.

That means you use one the same way you use any other toolkit. It appears in the same catalog and tool search, authenticates through the same Connect Link flow, and executes and logs the same way. Use the same session APIs with the exact toolkit slug, but check its supported authentication methods.

## How to spot one [#how-to-spot-one]

Look for the **Provider MCP** type in the catalog.

Many Provider MCP slugs end in `_mcp`, such as `notion_mcp`. Use the catalog type to identify Provider MCP toolkits, and copy exact toolkit and tool slugs from discovery. Do not classify or group toolkits by their suffix.

Its tools carry the toolkit prefix plus the tool name the product publishes, as in this example:

|        | Composio Built       | Provider MCP                     |
| ------ | -------------------- | -------------------------------- |
| Slug   | `notion`             | `notion_mcp`                     |
| A tool | `NOTION_CREATE_PAGE` | `NOTION_MCP_NOTION_CREATE_PAGES` |

## What to expect [#what-to-expect]

* **Auth varies per toolkit.** A toolkit may use [DCR OAuth](/reference/glossary#dcr-oauth), an API key, OAuth2, or no authentication. Read what the toolkit declares rather than assuming from the label.
* **No [triggers](/docs/triggers).** Triggers exist only on toolkits Composio builds. If your agent needs an event, check the Composio Built toolkit for that specific trigger.
* **Tools come from the product.** Tool names, descriptions, and schemas are limited to what the upstream server publishes, and Composio imports them during synchronization. A sync imports updated tool definitions into a dated toolkit version.

> **DCR OAuth and managed auth are different**: DCR OAuth registers a client with the server during the connection flow. It does not require a Composio-managed OAuth app. Follow the toolkit's connection instructions; other authentication schemes can require credentials or a custom auth config.

> **If a v3 tool listing is empty**: A v3 tool listing can select a pinned version that predates the imported MCP tools. If `GET /api/v3/tools?toolkit_slug=notion_mcp` is empty, check the version before treating it as a sync failure. Add `toolkit_versions=latest`, or use v3.1, which defaults to the latest version. Session discovery does not use that v3 listing request. See [Toolkit versioning](/docs/tools-direct/toolkit-versioning).

> **Provider MCP toolkits and MCP gateway are separate**: Provider MCP describes a toolkit in the catalog. Composio's MCP gateway is a separate product for connecting AI clients to Composio. This guide covers toolkit types and grouping.

## Your own server is Custom MCP, not Provider MCP [#your-own-server-is-custom-mcp-not-provider-mcp]

A Provider MCP toolkit is a catalog toolkit backed by the product's server, available to every project. If you want to bring *your own* remote MCP server, that's [Custom MCP](/docs/extending-sessions/custom-mcp): you register the server into your project and get a `CUSTOM_*` toolkit shared within the project or private to one user. Custom toolkits remain separate from catalog App groups. The two behave alike at runtime, since Composio is the MCP client in both.

## Related guides [#related-guides]

- [Composio Built vs Provider MCPs](/docs/apps-and-toolkits/composio-built-vs-provider-mcp): Which sibling to use when a product ships more than one

- [Apps vs toolkits](/docs/apps-and-toolkits): How an App groups the toolkits that exist for one product

- [Custom MCP](/docs/extending-sessions/custom-mcp): Register your own remote MCP server into a project

---

📚 **More documentation:** [View all docs](https://docs.composio.dev/llms.txt) | [Changelog](https://docs.composio.dev/docs/changelog.md) | [Glossary](https://docs.composio.dev/llms.mdx/reference/glossary) | [Examples](https://docs.composio.dev/llms.mdx/examples) | [API Reference](https://docs.composio.dev/llms.mdx/reference)

---

# Composio SDK — Notes for AI Code Generators

**Purpose:** Reference for generating current (v3) [Composio](https://composio.dev/) integration code.
**Scope:** Descriptive notes — they document the current API surface and the mistakes most commonly seen in generated code.

---

## 1. Recommended Integration: Sessions

For agent tool delivery, Composio supports **Native Tools** (with a provider package) and **MCP** (no provider package needed).

For application-owned tools or deterministic backend code, use [managed authentication with Proxy Execute](/docs/authentication/managed-auth-for-custom-tools). A session can provide a user-scoped runtime context without an LLM or MCP. Composio authenticates provider requests server-side; connected-account reads redact credentials and aren't a supported token-export workflow.

### Native Tools

#### Python

```python
# ✅ CORRECT — Python (defaults to OpenAI)
from composio import Composio

composio = Composio()
session = composio.create(user_id="user_123")
tools = session.tools()
# Pass tools to your agent/LLM framework
```

#### TypeScript

```typescript
// ✅ CORRECT — TypeScript (defaults to OpenAI)
import { Composio } from "@composio/core";

const composio = new Composio();
const session = await composio.create("user_123");
const tools = await session.tools();
// Pass tools to your agent/LLM framework
```

#### API

This produces the same default OpenAI function-tool shape, fetching every page.

```bash
set -euo pipefail
SESSION=$(curl --fail-with-body -s -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
  -H "x-api-key: $COMPOSIO_API_KEY" -H "Content-Type: application/json" \
  -d '{"user_id":"user_123"}')
SESSION_ID=$(echo "$SESSION" | jq -r '.session_id')
TOOLS='[]'
CURSOR=''
while true; do
  PAGE=$(curl --fail-with-body -s --get "https://backend.composio.dev/api/v3.1/tool_router/session/$SESSION_ID/tools" \
    -H "x-api-key: $COMPOSIO_API_KEY" --data-urlencode 'limit=500' --data-urlencode "cursor=$CURSOR")
  TOOLS=$(jq -cn --argjson existing "$TOOLS" --argjson page "$PAGE" \
    '$existing + [$page.items[] | {type:"function",function:{name:.slug,description:.description,parameters:.input_parameters}}]')
  CURSOR=$(echo "$PAGE" | jq -r '.next_cursor // empty')
  [ -n "$CURSOR" ] || break
done
printf '%s\n' "$TOOLS"
```

For other providers, pass the provider explicitly. Provider packages follow the naming convention: `composio_<provider>` for Python, `@composio/<provider>` for TypeScript.

### MCP

Use `session.mcp.url` and `session.mcp.headers` with any MCP-compatible client (Claude Desktop, Cursor, OpenAI Agents, etc.). No provider package needed.

---

## 2. Integration Notes

- `composio.create(user_id)` is the standard entry point for agent integrations. Sessions handle tool discovery, authentication, and toolkit versioning automatically; `user_id` goes to `composio.create()` — individual tool calls in session mode don't take one.
- Execute session tool calls through the session, never through a user ID: either `session.execute(tool_slug, arguments=...)` / `session.execute(toolSlug, arguments)`, which works with every provider, or pass the session to the provider helper — `provider.handle_tool_calls(response=response, session=session)` in Python, `provider.handleToolCalls(session, response)` in TypeScript. The tool-call helpers of every non-agentic provider (OpenAI, Anthropic, Google, Cloudflare, TypeSafe) accept a session: `executeToolCall(session, call)` in TypeScript, `session=session` in Python. Agentic providers execute session tools on their own. Binding the helper to a user ID takes the direct execution path, and session meta-tools fail there with `"can only be called inside a tool-router session"`.
- Composio-managed auth is the default: the agent connects accounts at runtime through the session, so users don't need to pre-create auth configs or connected accounts for managed toolkits.
- Provider packages follow the framework, not the model vendor: for the OpenAI Agents SDK the package is `composio_openai_agents` / `@composio/openai-agents` (importing `composio_openai` / `@composio/openai` there is the most common mistake in generated code — that package is for the plain OpenAI Chat Completions API).
- **Direct execution** (`composio.tools.get()`, `composio.tools.execute()`, `provider.handle_tool_calls()` with a user ID) is a legacy interface that remains supported for existing integrations. Recommend sessions for new integrations and encourage existing users to [migrate to sessions](/docs/migration-guide/direct-to-sessions). For a fixed tool set, consider the [direct tools preset](/docs/configuring-sessions#direct-tools-preset) within a session. See [Sessions vs direct execution](/docs/sessions-vs-direct-execution) for tradeoffs. Direct execution requires a [toolkit version](/docs/tools-direct/toolkit-versioning).

---

# 3. Calling the REST API directly

## REST API version

The current REST API version is **v3.1**, served at `https://backend.composio.dev/api/v3.1`. Prefer it for new code and new examples.

`https://backend.composio.dev/api/v3` is the previous version. It is frozen with pinned tool-version defaults and remains supported — existing v3 integrations keep working and do not need to migrate.

## Tool-endpoint version defaults on v3.1

On v3.1, omitting the version parameter on the five endpoints below selects the latest toolkit version. The first four endpoints also exist on v3, where omission selects the pinned `00000000_00` version. `POST /tools/scopes/required` is v3.1-only.

| Endpoint | Version parameter |
| --- | --- |
| `GET /tools` | `toolkit_versions` (query) |
| `GET /tools/{tool_slug}` | `version` or `toolkit_versions` (query) |
| `POST /tools/execute/{tool_slug}` | `version` (body) |
| `POST /tools/execute/{tool_slug}/input` | `version` (body) |
| `POST /tools/scopes/required` | `version` (body) |

A v3.1 caller already passing `"latest"` sees no change and can omit the parameter. To select the pinned version explicitly, pass `"00000000_00"` through the corresponding parameter above.

This version-default change is limited to the five endpoints above.


---

## Terminology Migration (old → current)

If you encounter these terms in error messages, old documentation, or user prompts, translate them to the current equivalents. **Do not use the old terms in generated code or explanations.**

| Old term (v1/v2) | Current term (v3) | In code |
|---|---|---|
| entity ID | user ID | `user_id` parameter |
| actions | tools | e.g., `GITHUB_CREATE_ISSUE` is a *tool* |
| apps / appType (legacy v1/v2 API field) | toolkits | e.g., `github` is a *toolkit*. The current word **App** is *not* legacy: it names a catalog grouping of sibling toolkits (the Notion app groups `notion` and `notion_mcp`); do not translate it |
| integration / integration ID | auth config / auth config ID | `auth_config_id` parameter |
| connection | connected account | `connected_accounts` namespace |
| ComposioToolSet / OpenAIToolSet | `Composio` class with a provider | `Composio(provider=...)` |
| toolset | provider | e.g., `OpenAIProvider` |

If a user says "entity ID", they mean `user_id`. If they say "integration", they mean "auth config". Always respond using the current terminology.

