# MCP Servers in Docs: Redocly vs Powerduck

**Short answer:** A docs platform adds MCP and AI search on higher tiers, which is useful for a portal; a studio generates the MCP server from the contract as a core capability, so an external agent can call the API correctly. The first serves the portal; the second serves the agent.

## What MCP in a portal does

Exposes tools and search around the documentation, usually on a higher hosted plan. It is a portal feature.

## What a generated MCP server does

| Property | Portal MCP | Generated server |
| --- | --- | --- |
| Source | Portal config | The contract |
| Plan gate | Higher tier | Core |
| Agent calls | Portal tools | API operations |
| Provenance | As configured | Visible |

## Why the distinction matters

A portal MCP is oriented around the docs; a generated server is oriented around the operations, so an agent performs the real API call correctly.

## The decision rule

Use the portal MCP for the documentation experience and the generated server for the agent's API calls. They serve different users.

This is part of the [Powerduck vs Redocly comparison](https://www.powerduck.com/blog/powerduck-vs-redocly/). Finish with [migrating to the studio](https://www.powerduck.com/blog/migrate-redocly-to-powerduck/).