@skeletiq/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKELETIQ_API_KEY | Yes | A personal API token, starting skq_. Not a browser session token. | |
| SKELETIQ_API_URL | No | For self-hosted installs. A trailing /api/v1 is accepted and trimmed. | https://api.skeletiq.com |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List the SkeletIQ projects this token can see, optionally filtered by name. Use this first to turn a project a person named in conversation into an id. If more than one project matches, ask which — do not pick one. |
| get_designA | Read a SkeletIQ architecture. Start with mode "brief" to orient — it returns a fenced block to write into AGENTS.md — then "build_order" for the sequence and "component" for each piece as you build it. Every answer states which version it came from and whether that version is a release. |
| generate_architectureA | Design a system architecture from a prompt. This spends the account holder's credits and takes several minutes, so do not call it speculatively — if a design already exists, read it with get_design instead. Which model runs it is the account holder's stored setting; you do not choose it. Describe the system, what it must do, and the scale and constraints it runs under: whatever the prompt leaves out is assumed, and a prompt that names no system at all comes back as clarification_required with the questions to answer. |
| get_generation_statusA | Check a background generation started with wait: false. When status is "completed", read the result with get_design. |
| critique_architectureA | Check a design against SkeletIQ's architecture rules and get scored findings back. Deterministic and free — no model call, no credits, nothing stored. Useful on a design you drafted yourself before committing to it. |
| check_driftB | Tell SkeletIQ which components you have built and get back what is missing, what is only half done, and what exists in the code but not in the design. Declare |
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 occupies a clearly distinct role: listing projects, reading existing designs, generating new ones, polling generation status, critiquing a design, and checking drift. There is no meaningful overlap between any pair.
All tool names follow the same lowercase snake_case verb_noun pattern (list_projects, get_design, generate_architecture, get_generation_status, critique_architecture, check_drift). The verbs are specific and consistently placed.
Six tools is a well-scoped size for an architecture design assistant. Each tool covers a distinct stage in the workflow without redundancy or bloat.
The surface covers the full lifecycle an agent needs: discover projects, read designs, kick off generation, poll for completion, critique a proposed design, and verify built code against the design. No operation essential to the stated purpose is missing.