mcpbeat

Qt Documentation MCP Server

io.qt.qt-docs-mcp/qt-documentation
answering

Qt Documentation is answering right now. Last checked 3 min ago. It exposes 2 tools.

Search Qt 6 API and product docs (Qt Core, Qt Quick, Qt Creator, Boot to Qt, MCUs).

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
62 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add qt-documentation --transport http https://qt-docs-mcp.qt.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "qt-documentation": {
      "url": "https://qt-docs-mcp.qt.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.qt-documentation]
url = "https://qt-docs-mcp.qt.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "qt-documentation": {
      "url": "https://qt-docs-mcp.qt.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "qt-documentation": {
      "url": "https://qt-docs-mcp.qt.io/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

documentation
qt_documentation_read
Read the full content of a specific Qt documentation page. Use the filename shown in search results.
qt_documentation_search
Call qt_documentation_search when: (a) you're about to claim a signal/slot/property/default exists, (b) the API is in Qt 6.7+ or a non-core module (MQTT, OPC UA, Network Auth, etc), (c) the user used the words 'docs', 'official', 'verify', or 'check'. Skip when: the question is about basic QString/QObject/signal-slot syntax.

Endpoints

URLTransportStateLatencyChecked
https://qt-docs-mcp.qt.io/mcp streamable-http answering 70 ms 3 min ago

Qt Documentation — questions

Answers built from our own checks of this server.

What can Qt Documentation do?
It exposes 2 tools, read directly from the server on our last check. Among them: qt_documentation_read, qt_documentation_search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Qt Documentation working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 62 ms. The bar chart above shows every period we have measured.
How do I connect Qt Documentation?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Qt Documentation need an API key?
No. Qt Documentation completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Qt Documentation?
It answers our handshake in 62 ms on average, which is faster than 96% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.