---
title: "Connect your own MCP servers"
description: "Let the AI in your MySpec sessions call tools from MCP servers you add, for yourself or for one project."
---

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

# Connect your own MCP servers

You can add your own [MCP](https://modelcontextprotocol.io) servers to
MySpec, such as your issue tracker or your internal documentation. The AI in
your spec sessions can then call their tools while it interviews you and
writes spec files.

This is the reverse of [Connect your coding agent](/mcp/):

| | Direction | Example |
|---|---|---|
| [Connect your coding agent](/mcp/) | Your agent uses MySpec | Claude Code reads your spec files from MySpec. |
| This page | MySpec uses your servers | The AI in a Generate session looks up tickets in your issue tracker. |

## Personal and project servers

You can add servers in two places:

| | Personal servers | Project servers |
|---|---|---|
| Where | **Profile** → **MCP Servers** | A project's **Settings** → **MCP servers** |
| Who manages them | You | Anyone with **Admin** on the project |
| Used in | Every project, for the messages **you** send | One project, for everyone working in its sessions |
| Maximum | 3 | 3 per project |

Your personal servers are not shared with teammates. When a teammate sends a
message, the AI uses their personal servers, not yours. Use a project server
when the whole team needs the same tools.

Both work in Generate and Edit sessions, for every workflow.

## Before you start

The server must:

- Be reachable over the internet at an address that starts with `https://`.
  MySpec does not connect to servers on your own computer or on a private
  network.
- Use the **Streamable HTTP** or **SSE** transport.

If the server needs an API key, have it ready. You send it as a header.

## Add a personal server

1. **Open your profile**

   Open the avatar menu, choose **Profile**, and scroll to **MCP Servers**.
   Select **Add server**.
2. **Name it**

   Enter a **Name**: letters, digits, hyphens and underscores, starting with
   a letter or digit. MySpec puts the name in front of the server's tool
   names. Don't include "mcp" in it; MySpec already marks the tools as MCP.
3. **Enter the address**

   Enter the server's **URL** and choose its **Transport**:
   **Streamable HTTP** or **SSE**.
4. **Add headers, if the server needs them**

   Select **Add header** and enter a **Header name** and **Header value**,
   for example an `Authorization` header with your API key. You can add up
   to 8 headers. Values are stored encrypted and never shown again.
5. **Save**

   Select **Save**. The server appears in the list with its transport.

## Add a server to a project

You need **Admin** on the project. Below Admin, the project's **Settings** menu
doesn't show **MCP servers**, but the project's servers are still used in your
sessions. See [Teams and project access](/guides/teams-and-project-access/).

1. **Open the project's settings**

   Open the project, select the **Settings** tab, then **MCP servers** in the
   menu on the left. The **MCP Servers** card says **Available only in this
   project's AI sessions**.
2. **Add it**

   Select **Add server** and fill in the form as for a
   [personal server](#add-a-personal-server).

When the list is full, **Add server** is disabled and the card says
**You've reached the maximum of 3 MCP servers.** Delete one to add another.

## What the AI does with your servers

For each message in a session, MySpec connects to the enabled servers that
apply: your personal servers and the project's servers. The AI sees their
tools next to its own and calls one when it helps with your request, for
example to look up an existing feature in your tracker before it writes
requirements.

- If a server doesn't respond, MySpec leaves it out for that message and
  the session carries on without it.
- If a personal server and a project server have the same URL, MySpec uses
  the project's entry.
- To see the tools the AI can use in a session, select **Inspect MCP Tools**
  in the chat header. It opens the **MCP Tools** panel.

> **Only add servers you trust**
>
> The AI decides when to call a tool and what to send it, based on your
> conversation. Add only servers you trust, and give any API key only the
> access the AI needs.

## Edit, disable or delete a server

Each server in the list has these actions:

| Action | What it does |
|---|---|
| **Edit** | Opens **Edit MCP server**. Existing header values are hidden: leave a value blank to keep it, or type a new one to replace it. |
| **Disable** | Keeps the server configured but stops sessions from using it. The list shows a **Disabled** badge. |
| **Enable** | Lets sessions use a disabled server again. |
| **Delete** | Removes the server from your AI sessions. Its stored API keys are deleted permanently. |

Chats that are already running pick up a change from their next message.

Source: https://docs.myspec.dev/guides/your-mcp-servers/index.mdx