One remote endpoint, added once. There is no package to install, no key to issue, and no account to create.
Endpoint
https://missingmanual.ai/mcp
Do not fetch that URL as a document. It is an MCP transport, not a page.
Claude Code
claude mcp add --transport http missing-manual https://missingmanual.ai/mcp
Cursor and other clients
Clients that keep an mcpServers map — Cursor in
~/.cursor/mcp.json, among others — take the endpoint
directly.
{
"mcpServers": {
"missing-manual": {
"url": "https://missingmanual.ai/mcp"
}
}
}
Optional agent skill
Compatible agents can use the MissingManual client skill for the create, capability, polling, and receipt sequence. The skill adds no service dependency; the MCP tool descriptions remain sufficient on their own.
What the agent sends
create_guide takes a topic, an
idempotencyKey, and
maxTotalChargeUsdMicros — the ceiling your agent authorizes,
in USD micros, as a whole number of cents. The payment credential travels in
MCP protocol metadata, not as a model-visible tool argument.
The server publishes the minimum authorization it will accept. A request below that minimum is refused rather than started at a price that cannot cover the run.
The call returns a job id and one opaque capability. Keep both. They are the only way to read the guide, and they are not recoverable.
Then
get_guide takes that job id and capability. While the run is
in flight it returns status and a suggested poll delay. Reads are free.
After the run finishes and the charge settles, the same call returns the
markdown and an itemized receipt.
A failed or cancelled run returns no markdown and charges $0.
Check the origin
curl -s https://missingmanual.ai/healthz
This reports whether the service is up and whether it is currently accepting paid runs. It starts nothing and costs nothing.