Qt Documentation

io.qt.qt-docs-mcpPublished by qt-docs-mcp.qt.ioOfficial publisherv0.3.0Updated Oct 24, 2026

Qt 5 and Qt 6 framework and product docs: Qt Creator, MCUs, Squish, Coco and more.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant look up Qt 5 and Qt 6 framework and product documentation, including Qt Creator, MCUs, Squish and Coco.

What you can do
This remote MCP server exposes Qt's official documentation as a lookup source for an assistant. According to the registry description, it covers the Qt 5 and Qt 6 frameworks plus related products such as Qt Creator, MCUs, Squish and Coco. No individual tools are listed in the manifest, so the exact query interface is not documented here.
When to use it
Useful when an assistant needs to answer questions about Qt APIs, framework versions, or Qt tooling and should ground those answers in official documentation rather than general knowledge. Less relevant if you do not work with Qt.
Requirements
A remote streamable HTTP endpoint at No authentication, environment variables, headers or packages are declared, so it appears to need only network access to that endpoint.
Before you install
The manifest declares no credentials, no write tools and no payments, and the description shows only documentation lookup. Because no tool list is published, confirm what the server actually exposes before relying on it. Queries are sent to a third-party endpoint operated by the provider.

Installation

In SourceWeft

  1. Open Qt Documentation in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.qt.qt-docs-mcp%2Fqt-documentation/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

2

qt_documentation_read

Read the full content of a specific Qt documentation page. Use the filename shown in search results.

Parametersfilerequiredversion

Version history

2
  1. v0.3.0LatestSep 28, 2026
  2. v0.2.0Sep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.