> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apigene.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Native MCP Servers

> Install and manage native MCP servers — official catalog, registry, and custom connections

## Overview

**Native MCP servers** are external Model Context Protocol servers you connect to Apigene (for example vendor MCP endpoints). They are different from **OpenAPI applications**, which Apigene turns into MCP tools automatically.

Use native MCP when you already have (or want) a remote MCP server. Use [Applications](/user-guide/applications) when you have an OpenAPI/Swagger spec or Postman collection.

After install, attach native MCP servers to [Agents](/user-guide/agents) so Co-pilot and the [MCP Gateway](/user-guide/mcp-gateway/mcp-gateway-overview) can use their tools.

<Note>
  Managing MCP servers is typically an **admin** capability. Availability may depend on your plan and deployment.
</Note>

## Accessing MCP Servers

Open **MCP** from the main navigation (or start from **Applications → Install Application → MCP Server**, which opens the official catalog).

From the MCP dashboard you can:

* Browse installed servers (search and sort)
* Install from the **official catalog** or **MCP registry**
* Create a **custom** MCP connection
* **Authorize**, **edit**, **test tools**, or **delete** a server

## Install from the official catalog

1. Go to **MCP → Official MCP Servers** (or **Install Application → MCP Server**)
2. Search by name or browse the list
3. Open vendor help links when you need auth or setup details
4. Click **Install** on the server you want
5. Complete any authorization the server requires (see [Authorize and reconnect](#authorize-and-reconnect))

Official entries typically include a display name, MCP URL, description, and optional website/help URL.

## Install from the MCP registry

1. Go to **MCP → Registry** (directory-style catalog)
2. Search and filter servers
3. Review metadata, then install into your organization
4. Authorize if the server requires OAuth or credentials

Use the registry when you need a broader directory beyond the curated official list.

## Custom MCP installation

Connect any remote MCP endpoint:

1. Go to **MCP → Custom MCP Installation** (create)
2. Enter a **name** for the server (unique in your org)
3. Enter the MCP **server URL**
4. Optionally add **HTTP headers** (for example API keys)
5. Optionally configure **OAuth** client id, secret, and scopes when the server uses OAuth
6. Save the configuration

You are returned to the MCP list when the server is created successfully.

## Authorize and reconnect

Some MCP servers require user or client authorization before tools work:

1. Open the MCP dashboard
2. Find the server and click **Authorize** when prompted
3. Complete the OAuth or credential flow in the browser
4. Use refresh/reconnect actions if tokens expire or tools fail to load

If tools stay empty after install, authorize first, then use **Test tools**.

## Test MCP tools

1. Open **Test tools** for an installed server
2. Review discovered tools and try sample invocations
3. Fix URL, headers, or OAuth settings if discovery fails
4. Save changes and re-test

## Attach native MCP to agents

1. Open **Agents** → select an agent → **Applications** (or MCP attachments area)
2. Add the native MCP server (not an OpenAPI→MCP bridge listed as an application)
3. Save the agent
4. Optionally restrict which gateway tools are exposed under **Setup → Enable MCP Tools**

In [Agent Builder](/user-guide/agent-builder), recommendations distinguish **APIs** (OpenAPI apps) from **installed MCP** (native servers). Prefer APIs for OpenAPI integrations; use native MCP only for real MCP endpoints.

## Native MCP vs OpenAPI applications

|                  | Native MCP                                   | OpenAPI application                |
| ---------------- | -------------------------------------------- | ---------------------------------- |
| Source           | Remote MCP URL / catalog                     | OpenAPI URL, file, or Postman      |
| Install UI       | MCP dashboard / official / registry / custom | Applications → OpenAPI based       |
| Tools            | Provided by the MCP server                   | Generated by Apigene from the spec |
| Attach to agents | As MCP server                                | As application / API               |

OpenAPI apps still appear as MCP tools inside Apigene and the gateway — you do not need a separate native MCP install for those.

## Related

* [Applications](/user-guide/applications) — OpenAPI and Postman installs
* [Agents](/user-guide/agents) — attach tools and MCP client setup
* [MCP Gateway](/user-guide/mcp-gateway/mcp-gateway-overview) — expose *your* agents to Claude, Cursor, and other clients
* [MCP Apps](/user-guide/mcp-apps) — UI templates for action results
* API: [MCP Server](/api-reference/mcp-server/mcp-server-create) reference