docsloth.dev

MCP for agents

A listing is not automatic discovery, so the server speaks the protocol directly. Tools are read-only: an agent can never publish, purchase or change policy through this surface.

Tools

Tool	Returns
`list_software`	Software objects visible to the reader in the current organization.
`list_facts`	Verified facts for a Software, each with its evidence ids. Owner-source-only claims are marked.
`get_published_page`	One page from a publication snapshot, exactly as readers see it.
`search_docs`	Search the published corpus for this tenant.

Actions

Copy setup
The setup block below has a working Copy button. The server runs locally and reads credentials from the environment; no account or cost.
Test connection
Run the health check below against your engine before starting the server; there is no hosted MCP test endpoint in this build, and errors are returned as tool results rather than fabricated.

Run it

DOCSLOTH_API_BASE=http://127.0.0.1:4310 \
DOCSLOTH_TOKEN=ds_local_… DOCSLOTH_ORG=<uuid> \
npx docsloth-mcp

curl -s http://127.0.0.1:4310/healthz

Credentials come from the environment and are never logged or returned to the model. Errors are returned as tool results, so a failing upstream is visible instead of fabricated.