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

> ## Agent Instructions
> Spur is an AI-powered QA engineer that lets teams create and run automated end-to-end tests for web and mobile apps using natural language.
> When answering questions about Spur, cite the relevant page from docs.spurtest.com.

# MCP Servers in Spur AI

> Connect remote MCP servers such as Linear, Notion, and Sentry to Spur AI, then approve each tool call it makes in chat.

## Overview

Connect remote Model Context Protocol (MCP) servers to [Spur AI](https://docs.spurtest.com/analysing-tests/spur-ai-chat.md) so it can use tools from products your team already works in. For example, Spur AI can look up a Sentry error or find a Linear issue while it helps you with a test.

The servers you connect are yours alone. Other people in your organization can't use them. Spur AI asks for your approval before it calls a tool on a connected server.

Admins choose which servers members can connect in each Application. See [Allow servers for your team](#allow-servers-for-your-team).

> [!NOTE]
>
> This page covers servers that Spur AI connects to. To connect your own AI assistant to the Spur MCP server, see [MCP Setup](https://docs.spurtest.com/analysing-tests/mcp/spur-mcp-setup.md).

## Connect a listed server

Spur lists these hosted MCP servers: Linear, Atlassian, ClickUp, Notion, Zendesk, Zephyr, qTest, Testiny, Sentry, Datadog, PostHog, Amplitude, Fullstory, Contentsquare, LaunchDarkly, Optimizely, Supabase, and Stripe.

**1. Open the MCP servers dialog**

In Spur AI, click the **MCP** button below the message box. The **MCP servers** dialog opens.

**2. Select a server**

Open the **Explore** tab and select a server. Use the search field to filter the list.

If you're a member, the servers you can't connect yet sit under **Needs admin approval**. Spur dims these servers. You can't select them. Ask an admin to allow the server you need.

**3. Enter the server's details**

Spur shows **Connect to** followed by the server's name. Most servers need no details. Datadog and Amplitude ask for a **Region**. Zendesk asks for your **Zendesk subdomain**. qTest asks for your **qTest site** and an **API token**.

Click **Back** to return to the list.

**4. Continue and sign in**

Click **Continue**. Spur sends you to the server's own sign-in page. Sign in and authorize Spur there. Spur never sees your password.

The server sends you back to the page you started from. The **MCP servers** dialog shows the server on the **Connected** tab.

qTest uses your API token instead of a sign-in page. Spur connects it when you click **Continue**.

Testiny accepts the sign-in only when you have a paid or trial Testiny plan and a Testiny admin has turned on **External App Access / OAuth2**.

If you cancel the sign-in or it fails, the server stays on the **Connected** tab with a **Sign-in needed** badge. Click **Sign in** to try again.

## Connect a custom server

A custom server is a remote MCP server that Spur doesn't list. An admin adds each custom server for the Application by its URL. You can then connect it. You can't add a server by its URL yourself.

Spur can't run local (stdio) servers.

If you're an admin, add the server for your team first. See [Add a custom server for your team](#add-a-custom-server-for-your-team).

**1. Select the server**

On the **Explore** tab, select the custom server. Custom servers sit at the top of the tab. Each tile shows the server's name, with the server's address under it.

If the server isn't there, ask an admin to add it.

**2. Check the server URL and name**

Spur shows **Connect to** followed by the server's name. Spur fills in **Server URL** with the address that the admin added. Change it to the server's full URL if the URL has a path, such as `/mcp`.

Spur fills in **Name** with the name on the server's tile. You can change it.

You can also paste the server's JSON config from Claude, Cursor, or VS Code into **Server URL**. Spur fills in the form from the config.

If you're a member, the form lists the servers you can connect. Spur doesn't connect a URL on any other server.

**3. Continue**

Click **Continue**. Spur connects to the server. If the server asks you to sign in, Spur sends you to its sign-in page.

### Advanced settings

Most servers connect with the URL alone. Click **Advanced settings** to change how Spur connects.

| Setting | What it does |
| - | - |
| **Description** | Says what the server is for. Spur AI reads it when it picks tools. |
| **Authentication** | **Automatic** is the default. It signs in with OAuth if the server asks. **Authorization header** sends a value you enter, such as an API key. **OAuth** signs you in on the server's own page. |
| **Transport** | **Auto** is the default. It uses Streamable HTTP and falls back to SSE. Select **HTTP** or **SSE** to use only that transport. |
| **Client ID** and **Client secret** | Appear when **Authentication** is **OAuth**. Both are optional. Enter them only for a server that doesn't let Spur register itself. |
| **Custom headers** | Click **Add header** to send an extra header with each request to the server. |

## Use connected tools in chat

Spur AI can use the tools of each server that is turned on and signed in. If you're a member, an admin must also allow the server for the Application. Describe what you need in plain language. Spur AI picks the tool.

Before each call, Spur AI shows an approval card that names the server and the tool. Click **Approve** to run the call, or **Deny** to skip it. The menu on **Approve** also lets you approve all later requests for that tool in the same chat.

If a server doesn't respond in time, Spur AI leaves its tools out of that message. Spur AI checks the server again on your next message.

## Manage your servers

Click the **MCP** button to open the **MCP servers** dialog. The button shows how many servers are connected, and a dot when a server needs sign-in.

The **Connected** tab lists your servers. Each server has a status badge:

| Badge | Meaning |
| - | - |
| **Connected** | Spur AI can use the server. |
| **Sign-in needed** | The sign-in expired or didn't finish. Spur AI skips the server until you click **Sign in**. |
| **Off** | You turned the server off. |
| **Not allowed** | An admin hasn't allowed the server for this Application. Spur AI skips the server until an admin allows it. |

Your connections follow you to every Application on your account. Each Application has its own allowed list. A server that works in one Application can show **Not allowed** in another.

For each server, you can:

* Use the switch to turn the server off without removing it. Use it again to turn the server back on.
* Open the actions menu and select **Details** to see the server's tools and who added it. See [View a server's details](#view-a-server’s-details).
* Open the actions menu and select **Edit** to change the server's settings. Changes apply from your next message. Leave a secret field blank to keep its saved value.
* Open the actions menu and select **Remove** to delete the connection.

### View a server's details

Open the actions menu on a server and select **Details**. The dialog shows the server's page, with its name, status badge, and description. For a listed server, the page also says what the server is for. Click **MCP servers** to return to the list.

**Tools** lists the tools that Spur AI can call on the server. Spur asks the server for its tools when you open the page. The list matches the tools that Spur AI gets in chat. Hover over or tap a tool to read its description.

When the server marks which of its tools only read data, Spur splits the list into **Read only** and **Can make changes**. The server decides which tools are read only. A tool that the server doesn't mark as read only goes under **Can make changes**.

Spur AI leaves out any tool it can't use, such as one whose definition is too large. When it leaves tools out, the page says how many.

Spur doesn't list the tools of a server that isn't allowed for the Application, or of a server that needs you to sign in. The page says why instead. If Spur can't reach the server, click **Try again**.

Under the tools, the page lists these details:

| Detail | What it shows |
| - | - |
| **Made by** | The company that makes the server, with a link to its site. Listed servers only. |
| **Category** | The kind of product the server belongs to, such as Issue tracking or Monitoring. Listed servers only. |
| **Server address** | The address that Spur connects to, without any query string. |
| **Connected by you** | When you connected the server. |
| **Sign-in** | How you sign in to the server: with your account on that product, with your API token, or not at all. |
| **Added for your team by** | The admin who allowed the server for the Application, and when. Appears only when the server is on the Application's allowed list. |

## Allow servers for your team

Admins choose which MCP servers members can connect in each Application. Members can connect only the servers on that Application's allowed list. Until an admin allows a server, members can't connect any. Admins also add a server for the team before they connect it themselves.

Allowing a server doesn't share a connection. Each member signs in with their own account. See [User Roles](https://docs.spurtest.com/additional-resources/user-roles.md) for what admins and members can do.

### Allow a listed server

**1. Open the Explore tab**

In Spur AI, click the **MCP** button below the message box, then open the **Explore** tab. The servers that members can't connect yet sit under **Needs admin approval**.

**2. Review the server**

Click **Add** on the server's tile. Spur shows what the server is for, who makes it, how members sign in, and the server address that it allows.

Zendesk and qTest also ask for your site. Enter your **Zendesk subdomain** or **qTest site**.

**3. Add the server for your team**

Click **Add for your team**. Click **Back** to return to the list without adding the server.

Spur confirms that it added the server for your team. Click **Undo** on the confirmation to remove the server again.

The servers you added sit under **Team approved MCPs** on the **Explore** tab. Select a server there to connect it yourself. For Datadog and Amplitude, **Add for your team** allows every region.

### Add a custom server for your team

Members can't add a server by its URL. Add each custom server for them. Only admins see the **Custom MCP** tile.

**1. Open the custom server form**

On the **Explore** tab, find the **Custom MCP** tile under **Needs admin approval** and click **Add**. Spur shows **Custom MCP servers**.

**2. Add the server**

Enter the server's address in **Server URL**. The address must be public and start with `https://`.

Spur keeps only the server's address and drops any path. For example, it saves `https://mcp.example.com/mcp` as `https://mcp.example.com`. Spur allows every path on that server.

Enter a name for the server in **Name (optional)**. A name can be up to 40 characters. Leave the field blank to use the server's own name.

Click **Add for your team**. Spur adds the server and clears the form, so you can add another. Click **Back** to return to the **Explore** tab.

If you leave **Name (optional)** blank, Spur asks the server for its name when you add it. Spur asks at the URL you entered. Include the server's path, such as `/mcp`, so Spur can reach the server. A server that asks for sign-in first, or that doesn't answer in time, gives no name. Spur then reads a name from the address, such as Example for `https://mcp.example.com`.

Everyone in the Application can then connect the server. It appears as its own tile at the top of the **Explore** tab. The server's name shows on the tile, in **Custom MCPs added**, and in **Team access**. Each member still signs in with their own account. To connect it yourself, see [Connect a custom server](#connect-a-custom-server).

The **Custom MCP** tile shows how many custom servers you added. **Custom MCP servers** shows the same count under its description, such as **2 custom MCPs added**. Click the count to open **Custom MCPs added**, which lists only your custom servers. Click **Back** to return to the form.

To rename a custom server, add its address again with the new name in **Name (optional)**. To stop allowing one, click **Remove** next to it in **Custom MCPs added**.

#### When the URL belongs to a listed server

A server that Spur lists can't be a custom server. When **Server URL** points to a listed server, such as Linear or Datadog, a note under the field names that server. Spur disables **Add for your team** while the note shows.

* If the note says the server is already added for your team, members can already connect it.
* If the note says the server is already available in Explore, click **Add** followed by the server's name, such as **Add Linear**. Spur opens the same card that [Allow a listed server](#allow-a-listed-server) describes. For Zendesk and qTest, Spur fills in your site from the URL you entered.

On that card, click **Add for your team**. Spur adds the server and returns you to **Custom MCP servers**. Click **Back** on the card to return to **Custom MCP servers** without adding the server.

### Review what your team can connect

On the **Explore** tab, click **Team access** next to **Team approved MCPs**. Spur lists the servers that members of the Application can connect. Click **Remove** next to a server to stop allowing it. Members' connections to that server stop working from their next message. Click **Undo** on the confirmation to allow the server again.

### Manage the allowed list on the Integrations page

You can also manage the allowed list on the Integrations page. The list shows each allowed server by its address.

**1. Open the allowed list**

Open the [Integrations page](https://app.spurtest.com/integrations). Find the **Allowed MCP servers** card under **Developer Tools** and click **Manage**. Only admins see this card.

**2. Allow the server**

Enter the server's address in **Server URL**, such as `https://mcp.linear.app`, then click **Allow**. The address must be public and start with `https://`. Spur allows every path on that server.

To stop allowing a server, click the trash icon next to it in the same dialog. Members who already connected that server see a **Not allowed** badge on it. Spur AI stops using its tools for them.

The card shows how many servers the Application allows, or **None allowed**.

## Limits

* You can connect up to 10 MCP servers.


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