Local stdio bridge for the hosted Docsie MCP server.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"docsie-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# docsie-mcp Local stdio bridge for the hosted Docsie MCP server. Use this package for MCP clients or directories that require a locally-run stdio server instead of a remote Streamable HTTP endpoint. ## Install Snippet ```json { "mcpServers": { "docsie": { "command": "uvx", "args": ["docsie-mcp"], "env": { "DOCSIE_MCP_TOKEN": "mcp_sa_...", "DOCSIE_MCP_ENDPOINT": "https://app.docsie.io/mcp" } } } } ``` `DOCSIE_MCP_ENDPOINT` defaults to `https://app.docsie.io/mcp`. ## Authentication The first version expects a Docsie MCP service token: ```bash export DOCSIE_MCP_TOKEN=mcp_sa_... uvx docsie-mcp ``` The token is sent as: ```text Authorization: Bearer <token> ``` The token still controls the selected Docsie organization, workspace, and permission packs.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.