# Qt Documentation MCP server

> Search and read Qt 5 and Qt 6 framework docs, plus Qt Creator, Design Studio, Qt for MCUs, Squish and Coco documentation.

- Listing: https://mcp.tc/i/qt-docs
- Connect: use the server's own URL `https://qt-docs-mcp.qt.io/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Docs & Knowledge](https://mcp.tc/c/docs-knowledge)
- Vendor: The Qt Company
- Homepage: <https://doc.qt.io/>

## About

Gives an assistant access to the official Qt documentation. It covers the Qt framework (Qt 6.12, 6.11, 6.8 LTS and Qt 5.15) and product docs for Qt Creator, Qt Design Studio, Qt for MCUs, Boot to Qt, Squish and Coco. Use it to check signals, slots, properties, default values and since-version details against the real source.

The server is hosted by The Qt Company at a streamable HTTP endpoint. No sign-in or API key is needed. A version parameter selects a specific Qt release; the latest is the default.

## What it can do

- Search Qt 5 and Qt 6 documentation
- Read the full content of a documentation page
- Target a specific Qt version such as 6.8 LTS or 5.15
- Look up Qt Creator, Design Studio, Qt for MCUs, Squish and Coco docs
- Verify signals, slots, properties and defaults before answering

## Tools (2)

- `qt_documentation_search`: Search Qt framework and product docs by query, with optional version, module, product and filter.
- `qt_documentation_read`: Read the full content of a Qt documentation page using the filename from search results.

## Example prompts

- "Does QtGrpc have a signal for stream completion in Qt 6.11? Check the docs."
- "Find the default value of QQuickItem::clip in Qt 6.8 LTS."
- "Search the Qt Creator docs for how to set up a CMake kit."
- "Read the Qt MQTT QMqttClient page and summarize its public slots."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http qt-docs https://qt-docs-mcp.qt.io/mcp
```

2. Start Claude Code and type `/mcp`. **qt-docs** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Qt Documentation** and paste this URL:

```url
https://qt-docs-mcp.qt.io/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Qt%20Documentation&connectorUrl=https%3A%2F%2Fqt-docs-mcp.qt.io%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://qt-docs-mcp.qt.io/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://qt-docs-mcp.qt.io/mcp` as the server URL and choose **No authentication**.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=qt-docs&config=eyJ1cmwiOiJodHRwczovL3F0LWRvY3MtbWNwLnF0LmlvL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "qt-docs": {
      "url": "https://qt-docs-mcp.qt.io/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=qt-docs&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fqt-docs-mcp.qt.io%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"qt-docs","type":"http","url":"https://qt-docs-mcp.qt.io/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "qt-docs": {
      "type": "http",
      "url": "https://qt-docs-mcp.qt.io/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "qt-docs": {
      "serverUrl": "https://qt-docs-mcp.qt.io/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add qt-docs --url https://qt-docs-mcp.qt.io/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.qt-docs]
url = "https://qt-docs-mcp.qt.io/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http qt-docs https://qt-docs-mcp.qt.io/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "qt-docs": {
      "type": "http",
      "url": "https://qt-docs-mcp.qt.io/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://qt-docs-mcp.qt.io/mcp`.

## Details

- Server version: 0.3.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-10-03 (reachable)
- Listed: 2026-10-03
- Updated: 2026-10-04

---
Source: https://mcp.tc/i/qt-docs (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report