Skip to content

Monoceros Docs

An agent in a workbench does not know how a Monoceros file looks, and the monoceros command does not run there for it to try. With this server the agent looks it up in the Monoceros docs: how a workbench template is written, which fields a service file takes, what an MCP server file needs. It also reads the component catalog. No credential, no sign-in.

Use it in a workbench where an agent writes Monoceros files, typically the one for your team’s template repository (Reuse and share your setup). The pages it serves include the template formats, with every field of each kind.

At init, or to an existing workbench:

Terminal window
monoceros init acme --with-mcp-servers=monoceros-docs
Terminal window
monoceros add-mcp-server acme monoceros-docs

Then apply:

Terminal window
monoceros apply acme

The yml entry is one line and your env file stays untouched:

mcpServers:
- name: monoceros-docs

Remote (http), at https://mcp.getmonoceros.build/mcp. The request leaves the container and carries no credential of yours, because there is none.

Terminal window
monoceros check acme
MCP servers
monoceros-docs → Claude Code
tools: search_docs, get_doc, list_components, get_component

Four tools: search the docs, read a page in full, list the catalog, read one component.

Terminal window
monoceros remove-mcp-server acme monoceros-docs