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.
What it’s for
Section titled “What it’s for”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.
Add it
Section titled “Add it”At init, or to an existing workbench:
monoceros init acme --with-mcp-servers=monoceros-docsmonoceros add-mcp-server acme monoceros-docsThen apply:
monoceros apply acmeThe yml entry is one line and your env file stays untouched:
mcpServers: - name: monoceros-docsWhere it runs
Section titled “Where it runs”Remote (http), at https://mcp.getmonoceros.build/mcp. The request leaves
the container and carries no credential of yours, because there is none.
Verify it
Section titled “Verify it”monoceros check acmeMCP servers monoceros-docs → Claude Code tools: search_docs, get_doc, list_components, get_componentFour tools: search the docs, read a page in full, list the catalog, read one component.
Remove it
Section titled “Remove it”monoceros remove-mcp-server acme monoceros-docsSee also
Section titled “See also”- MCP servers overview - the model behind this.
- Template formats - the pages the agent looks up.