MCP Server
Installable bridge that lets coding agents query Creatorem docs capabilities and page content.
What It Does
@creatorem/mcp-server exposes stable MCP tools over stdio so coding agents can:
- list documentation capabilities from
/mcp-index.json - resolve capability details and related pages
- fetch LLM-ready page content from
/llms.mdx/* - search capabilities by ID, title, tags, aliases, and description
Why it matters
This server gives agents structured retrieval first, then full page content only when needed.
When To Use
- You want Claude/Cursor/VS Code agents to understand the Creatorem API surface quickly.
- You want consistent, tool-based retrieval instead of prompt-only guessing.
- You want to keep docs consumption aligned with the generated MCP capability index.
Prerequisites
- Node.js
>=20 - Access to your hosted docs endpoints (
/mcp-index.json,/llms.mdx/*)
Install And Configure
Install or run directly with npx:
Optional environment variables:
CREATOREM_MCP_BASE_URL=https://creatorem.com
CREATOREM_MCP_TIMEOUT_MS=10000
CREATOREM_MCP_CACHE_TTL_MS=60000Add it to your MCP client config.
{
"mcpServers": {
"creatorem": {
"command": "npx",
"args": ["-y", "@creatorem/mcp-server"],
"env": {
"CREATOREM_MCP_BASE_URL": "https://creatorem.com"
}
}
}
}Ask the agent to call MCP tools first, then retrieve full page content only for selected pages.
Available Tools
| Tool | Purpose |
|---|---|
creatorem.list_capabilities | List/filter capability catalog |
creatorem.get_capability | Return one capability with related pages |
creatorem.get_page_content | Fetch LLM-ready text for a docs page |
creatorem.search_capabilities | Ranked search over capability metadata |
Troubleshooting
Upstream Unavailable
If tools return UPSTREAM_UNAVAILABLE, verify CREATOREM_MCP_BASE_URL and confirm /mcp-index.json is reachable.
- If tool calls return
INVALID_INPUT, check required keys (capabilityId,pageUrl,query). - If results are stale, lower
CREATOREM_MCP_CACHE_TTL_MSduring debugging.
MCP Context
capability: mcp_server_integration entrypoints: - packages/mcp-server/src/cli.ts - packages/mcp-server/src/tools.ts - apps/creatorem/content/.generated/mcp-index.json - apps/creatorem/app/mcp-index.json/route.ts - apps/creatorem/app/llms.mdx/[...slug]/route.ts inputs: - mcp_client_configuration - docs_base_url outputs: - structured_docs_capability_retrieval - llm_ready_page_content_for_agents constraints: - requires Node.js 20+ - docs endpoints must be reachable from MCP client runtime side_effects: - outbound HTTP calls to docs endpoints
Related
CLI
Commands to bootstrap and reshape projects with feature-level control.
Structure
How the monorepo is organized and where to implement each concern.
How is this guide?
Last updated on 3/24/2026