# MCP or API: how much of a product can an AI agent run through each?

At 108 of 123 products with both an API and an MCP server, an AI agent can reach fewer of the product's features through MCP than through the API.

Drives: 1 Oct 2026 to 1 Nov 2026 · 123 products · Step: [Use](https://agentdrives.com/access/use.md) · Subject: API coverage · Counted 1 Nov 2026. Source: https://agentdrives.com/findings/mcp-vs-api?via=md · CC BY 4.0

## What we found

| Route | Features it reaches | Share |
|---|---|---|
| API | 2,346 of 3,955 | 59% |
| MCP server | 1,232 of 3,955 | 31% |

| Route | Features run | Finished | Done in part | Needed a paid plan | Stopped |
|---|---|---|---|---|---|
| API | 2,054 | 831 | 77 | 156 | 990 |
| MCP server | 297 | 173 | 18 | 36 | 70 |

- 13 of the 123 reach more features through MCP than through the API.
- 208 of their 3,955 features are reachable only through MCP.
- 1,401 of their 3,955 features have neither an API endpoint nor an MCP tool.
- Our agent finished 40% of the features it ran through the API and 58% of those it ran through MCP.
- Through MCP, 12% of the features it ran needed a paid plan. Through the API, 8% did.
- It finished at least one feature through MCP at 24 of the 50 products where it used MCP, and through the API at 68 of the 148 where it used the API.

## For product owners

- List on your MCP server's docs page which features it covers and which need the API.
- Give the MCP server the work agents come for: create, read back, change and delete the product's main objects.
- Let the key an agent gets for the API work for the MCP server too.

## For agent builders

- Check the API when the MCP server lacks a feature.
- Read the plan rules before you call a tool. A tool can be listed and still need a paid plan.

## How we tested

- Drives from 1 Oct 2026 to 1 Nov 2026, 201 products. The docs of 123 of them name an API endpoint for at least one feature and an MCP tool for at least one.
- For each product we list its features from its docs, each with the API endpoint and the MCP tool the docs name for it.
- Our agent ran each feature through one route. A feature counts as finished when our agent read the result back and it matched.
- The results by route count every product we drove where our agent ran a feature that way: 148 through the API, 50 through MCP.

## Limits

- Each product's docs and MCP server as they were on the day of its drive.
- Each feature ran through one route, so the two results count different features.
- A product our agent didn't get into has no results by route.
- Counts under 5 are left out.

## Sources

- [Every number on this page, with its definition](https://agentdrives.com/data/facts.md?via=md#route.both)
- [Agent access: Use](https://agentdrives.com/access/use.md)
- [The MCP standard](https://agentdrives.com/standards/mcp.md)
- [How we drive](https://agentdrives.com/method.md?via=md)