API Tools
documesh.dev
MCP server for Documesh that manages documentation source ingestion, lists API endpoints and OpenAPI contracts, verifies user configs against documented keys, and reports documentation issues.
ENDPOINT 1
https://documesh.dev/mcp/product
MCP server metadata
- Name
- documesh-product
- Version
- 0.2.0
Known tools 7
service_statusGet Documesh service status, vendor count, API version, and the sandbox URL.
Inferred read-onlylist_api_surfaceList the Documesh API endpoints and where the OpenAPI contract lives.
Inferred read-onlyreport_issueReport a documentation problem (outdated/incorrect/misattributed chunk).
Inferred read-onlycontribution_statsGet mesh contribution counters: submissions, issue reports, sources indexed.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.documesh-product]
url = "https://documesh.dev/mcp/product"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"documesh-product": {
"type": "http",
"url": "https://documesh.dev/mcp/product"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: documesh-product
Remote MCP URL: https://documesh.dev/mcp/product
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"documesh-product": {
"url": "https://documesh.dev/mcp/product"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"documesh-product": {
"type": "http",
"url": "https://documesh.dev/mcp/product"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "documesh-product",
"transport": "streamable-http",
"url": "https://documesh.dev/mcp/product"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.