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

# MCP Server

> Enable a per-project MCP Server so your project's users and agents can query its data from an AI assistant. It is data-only, inherits each user's project roles, and has its own name, icon, and description.

The **MCP Server** is a per-project connector for your project's own data. When you enable it, your project's users and their AI agents connect from a tool like Claude, Cursor, or ChatGPT. The surface is **data-only**, and each user signs in with their project identity and inherits their project roles, or authenticates with a project API key.

It is separate from the account-level [Archie MCP](https://archie.com/docs/mcp/archie-mcp.md).

## Enable it

**1. Open the panel**

Open your project, go to **Backend**, then **Core Services**, and select **MCP Server**.

**2. Turn it on**

Switch the **MCP Server** toggle on. The **Server identity**, **Connect an assistant**, and **Tools** cards appear below it.

While the toggle is off, the panel shows only the **MCP Server** card.

![The MCP Server panel under Backend, Core Services, with the toggle off](https://mintcdn.com/archie-e998dbf6/Lv07l3TYoPUeWEyf/images/47-mcp-server-disabled.png?fit=max\&auto=format\&n=Lv07l3TYoPUeWEyf\&q=85\&s=149194a031751eaacbc0e9e9bb9ed811)

> [!NOTE]
>
> Enabling the MCP Server doesn't open your data to everyone. Users authenticate as themselves and act with their own [project roles](https://archie.com/docs/backend/app-services/role-based-access.md).

## Server identity

The **Server identity** card sets the name, icon, and description that connecting assistants show for this server. All three are optional. Leave them blank to use the defaults.

| Field | What you enter | Limit |
| - | - | - |
| **Name** | The name for this server, for example `Acme Production`. | 64 characters |
| **Icon** | An emoji, or an `https` URL to a logo image. Assistant directories use the URL form. | 2,048 characters |
| **Description** | What this server gives access to. | 500 characters |

Edit the fields and click **Save**. Archie confirms with **Server identity saved**.

## Authentication

The **Connect an assistant** card tells you how users connect. The message depends on the [authentication providers](https://archie.com/docs/backend/app-services/authentication-providers.md) that are active on your project:

* **Sign-in (identity).** Active providers of type Archie Identify, OAuth2, Google, Microsoft, Cognito, or Shiro. Connecting opens a login window, and there is no token to paste.
* **API keys.** Active providers of type API key or API token. Users paste a project API key as the `Authorization` header. The configuration in the panel includes the header with the placeholder `YOUR_PROJECT_API_KEY`. Create keys under [API Keys](https://archie.com/docs/backend/settings/api-keys.md).
* **Both.** Users choose either. The configuration in the panel uses an API key. Users leave it out to sign in instead.

> [!WARNING]
>
> If no authentication provider is active, the card shows **No authentication provider is active yet**, and users can't connect. Enable one under [Authentication Providers](https://archie.com/docs/backend/app-services/authentication-providers.md) first.

## Tools

The **Tools** card controls which tools assistants can use. The default set is data-only: introspection, `execute_graphql_operation`, `semantic_search`, docs, and context. Until you curate the set, the card shows **Using the default data-only tool set**.

When the card lists tools, each tool has its own switch. Turn a tool off to withhold it. You can narrow the data-only set, but you can't add tools beyond it.

## Permissions

The MCP Server doesn't widen access. A connected user acts with their own project role, and [Role-Based Access](https://archie.com/docs/backend/app-services/role-based-access.md) decides what that user can do.

## Next step

To connect a tool, see [Connecting an assistant](https://archie.com/docs/mcp/connecting.md).

## FAQ

> [accordion] Does enabling the MCP Server expose all my data?
>
> No. Users authenticate as themselves and act with their own project roles. The surface is data-only.

> [accordion] Is this the same as the Archie MCP?
>
> No. The [Archie MCP](https://archie.com/docs/mcp/archie-mcp.md) is account-level Agent Access that you approve in your browser. The MCP Server belongs to one project and works with that project's data.

> [accordion] Why doesn't my icon show up in the assistant?
>
> Assistants that add a server by URL can show their own avatar instead. The `https` URL form of the icon is the one assistant directories use.

> [accordion] Is the configuration per environment?
>
> Yes. The panel reads and saves enablement, identity, and tools for the environment you have selected. The server URL for any environment other than `master` ends in `?environment=<name>`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.