ultimate-construct3-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| projectPath | No | Path to your Construct 3 project. If omitted, only documentation features are available. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Full-text search across Construct 3 documentation. Returns matching topics with relevance-scored snippets. |
| get_docB | Get the full markdown content of a Construct 3 documentation topic. |
| list_topicsB | List all available Construct 3 documentation topics, optionally filtered by category. |
| list_categoriesB | List all documentation categories with descriptions and topic counts. |
| get_ace_referenceB | Get the Actions, Conditions, and Expressions (ACE) reference for a Construct 3 plugin or behavior. |
| get_examplesB | Search for code examples and snippets from the Construct 3 documentation. |
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 6 tools
Each tool targets a distinct facet of the docs surface (search, browse topics, browse categories, fetch topic, ACE reference, examples). The only mild overlap is between search_docs and get_examples, since both are query-style lookups, but the example-specific description makes the boundary clear enough.
All names follow a clean verb_noun snake_case pattern (search_*, list_*, get_*), with verbs matching the operation type. No mixed conventions.
Six tools is a well-scoped set for a documentation lookup server — one query tool, one content fetcher, two browsing tools, plus ACE and example lookups. Each earns its place without redundancy.
The surface covers the full docs workflow: browse categories/topics, search, fetch full content, and specialized ACE/example lookups. Minor gaps exist (e.g. no versioned docs or plugin-name discovery for ACE), but agents can work around them via search.