GPUI Kit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
GPUI Kit is a Rust desktop framework built on GPUI, with gpui-base primitives, gpui-component widgets and gpui-shell JavaScript hosting. Use search_docs to find relevant pages, then get_doc to read the full Markdown page (optionally one section at a time). Use list_docs or get_docs_index to browse the catalog. Documentation is available in English and Chinese (zh-CN).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Full-text search across all GPUI Kit documentation (guides, gpui-base primitives, components, gpui-shell). Returns matching pages with title, path, description and a content snippet. Start here, then call get_doc with the returned path. |
| get_docA | Read a GPUI Kit documentation page as Markdown. Accepts a path from search_docs (for example /component/button.md) or a page title/slug such as "Button". Use |
| list_docsA | List GPUI Kit documentation pages, optionally filtered by language, section, or a keyword matched against title and description. Useful for browsing what is available before reading a page. |
| get_docs_indexA | Return the collected https://gpui-kit.com/llms.txt index: every documentation page with its path and one-line description. Filter by language or section to keep the response small. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
get_doc is clearly distinct as the read tool, but search_docs, list_docs, and get_docs_index all return lists of documentation pages with paths and descriptions. The descriptions hint at differences (full-text search vs. keyword browse vs. llms.txt index), but an agent can easily pick the wrong one, especially list_docs vs. get_docs_index which both filter by language and section.
All names are snake_case verb_noun (search_docs, get_doc, list_docs, get_docs_index), which is predictable. Minor deviation: get_doc uses a singular object while get_docs_index embeds a plural compound noun, so the pattern isn't perfectly uniform.
Four tools is a sensible, well-scoped surface for a documentation server: one search, one read, and two browsing helpers. The only quibble is that the two listing tools partly overlap, so the set could arguably be three.
The core docs workflow is covered end to end: discover (search/list/index), then read a page with section-level granularity and path disambiguation. No obvious dead ends, though there is no tool for retrieving runnable examples or API signatures beyond what the Markdown pages contain.