> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/mcp-server-setup-guide.md).

# Set up the Siit MCP server

Connect the Siit MCP server to Claude, Claude Code, Codex, Mistral, ChatGPT, Cursor, Windsurf, Zed or another MCP client, with Public API permission and troubleshooting

### Before you start

* You need a Siit account with access to your workspace
* The Siit MCP server endpoint is `https://mcp.siit.io/mcp`
* The **Public API** feature must be enabled for your role. You can turn this on under Settings → Role & permissions → Public API.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-32fb947f66710d2c0c91ea2288afd94852c652ae%2FCleanShot-2026-06-10-at-17-09-58-png.png?alt=media" alt=""><figcaption></figcaption></figure>

### Claude (Desktop and Web)

Siit is listed in Claude's connector directory, so most people won't need to enter anything by hand.

1. Open **Customize**, then **Connectors**.
2. Browse or search for **Siit** in the directory.
3. Click **Connect** and authorize with your Siit account.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-d2c74a97985e52a0c71af976a09d36f46f6163b4%2FCleanShot-2026-08-07-at-18.00.06-2x.png?alt=media" alt=""><figcaption></figcaption></figure>

### Claude Code

Run the following in your terminal:

claude mcp add --transport http siit `https://mcp.siit.io/mcp`

Then open a Claude Code session and run /mcp to complete the authentication flow.

### Codex — Via CLI

Run:\
`codex mcp add siit --url https://mcp.siit.io/mcp`

You'll be prompted to log in with your Siit account automatically.

Note: If this is your first time using an MCP in Codex, you need to enable the `rmcp` feature first. Add the following to `~/.codex/config.toml:`

```
[features]
experimental_use_rmcp_client = true
```

Codex — Via config file

1. Open `~/.codex/config.toml`. in your preferred editor
2. Add the following:

toml

```
[features]
experimental_use_rmcp_client = true

[mcp_servers.siit]
url = "https://mcp.siit.io/mcp"
```

3. Run `codex mcp login siit` to complete authentication.

### Mistral

1. In Mistral, open the MCP connectors settings and select Custom MCP Connector.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-ec0c6009f418feaad76e5e3516c4898f7ac9f930%2FCleanShot-2026-06-12-at-16-20-21-png.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Enter Siit as the Connector Title.
3. Set the Connector Server to `https://mcp.siit.io/mcp`
4. Leave Description blank (optional).
5. Set Visibility to Workspace so the connector is shared with your team.
6. Leave Authentication Method on Auto-detect.
7. Click Create and authorize when prompted.

<figure><img src="https://2274035325-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlWFhpq2ia6gdHet0opKx%2Fuploads%2Fgit-blob-b789c12f63cc5e1afc26b0ac1cdd3628a8b2ff89%2FCleanShot-2026-06-12-at-16-21-35-png.png?alt=media" alt=""><figcaption></figcaption></figure>

Once connected, Siit appears under Connected in your Mistral connectors list.

### ChatGPT

Siit connects to ChatGPT as a custom connector.

1. In ChatGPT, open **Settings → Connectors** and select **Create**.
2. Enter **Siit** as the connector name.
3. Set the **MCP Server URL** to `https://mcp.siit.io/mcp`.
4. Set **Authentication** to **OAuth**.
5. Open **Advanced OAuth Settings** and make sure **Dynamic Client Registration** is enabled. ChatGPT does not turn this on by default, and leaving it off is the most common cause of connection errors with this client.
6. Click **Create**, then authorize with your Siit account.

> **Note**: If you see *"There was a problem connecting Siit.io MCP. Try again later."* after removing and re-adding the connector, check that Dynamic Client Registration is still enabled under Advanced OAuth Settings.

### Cursor

Visual Studio Code

1. Press `Ctrl/Cmd + P` and search for MCP: `Add Server.`
2. Select Command (stdio).
3. Enter the following command and press Enter:

   `npx mcp-remote https://mcp.siit.io/mcp`
4. Name the server Siit and press Enter.
5. Go to MCP: List Servers, select Siit, then select Start Server

### Windsurf

1. Press `Ctrl/Cmd +` , to open Windsurf settings.
2. Scroll to Cascade → MCP servers.
3. Select Add Server → Add custom server.
4. Paste the following configuration:

   `{`

   `"mcpServers": {`

   `"siit": {`

   `"command": "npx",`

   `"args": ["-y", "mcp-remote", "https://mcp.siit.io/mcp"]`

   `}`

   `}`

   `}`

### Zed

1. Press `Cmd +` , to open Zed settings.
2. Add the following:

```
{
"context_servers": {
"siit": {
"source": "custom",
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.siit.io/mcp"],
"env": {}
}
}
}
```

### Other MCP-compatible tool

For any other client that supports MCP:

* Command: `npx`
* Arguments: `y mcp-remote https://mcp.siit.io/mcp`
* Environment: None

### Troubleshooting

#### I see an "internal server error" when connecting

Clear saved auth data and try again:\
`rm -rf ~/.mcp-auth`\
You may also need to update Node.js to a more recent version.

#### Does the MCP support Streamable HTTP?

Yes — at `https://mcp.siit.io/mcp`

#### Which version of Node.js do I need?

We recommend the latest LTS version. If you run into issues, updating Node is the first thing to try.

\*\*Can I pull satisfaction survey ratings through the MCP or the API?\
\*\*Yes. Requests returned by `get_request`, `list_requests`, and the Public API's `/v1/requests/{uid}` endpoint now include a `satisfaction_survey_rating` field, the rating the employee left after the request closed, or empty if they never responded. You don't need a separate call or an `expand[]` parameter; it comes back with the rest of the request data automatically. This is the easiest way to pull CSAT into an external dashboard instead of using manual exports.

\*\*Can I manage Group Requests through the MCP or the API?\*\*\
Yes. New MCP tools create, read, and manage a request group, and the Public API's request endpoints understand groups too. Available on all plans.

\*\*Can I approve or reject app access requests through the MCP or the API?\*\*\
Yes. The Public API returns an app access request's app, status, and full timeline, and two new MCP tools let an agent approve or reject a pending request directly, so a backlog of access decisions can be worked through end to end without opening the admin console. Available on the Pro plan.

**Can I manage team inboxes, SLA rules and approval policies through the MCP or the API?**\
Yes. You can create and update team inboxes and their members, set a service's default assignment, and create and update SLA rules and approval policies. Assist uses the same tools, so asking it to change an SLA or assign a service no longer ends with a new workflow.

**Can I manage People groups through the MCP or the API?**\
Yes. You can create, rename and delete teams, departments, office locations and legal entities, and add people to them or take them out.

**Can I manage request tags through the MCP?**\
Yes. You can create, rename and delete request tags, and filter requests by inbox and by tag when you list them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.siit.io/guides/integrations/mcp-server-setup-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.