check_status — docracy MCP Tool Read-only
check_status
(check status) is one of 4 tools on the
docracy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_status from your client
- Claude Code docracy check_status run in your project directory
- Claude Desktop docracy check_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor docracy check_status ~/.cursor/mcp.json
- VS Code docracy check_status .vscode/mcp.json
- Zed docracy check_status ~/.config/zed/settings.json
- Windsurf docracy check_status ~/.codeium/windsurf/mcp_config.json
- Cline docracy check_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI docracy check_status ~/.gemini/settings.json
- Grok docracy check_status .mcp.json (in your project root)
- ChatGPT docracy check_status Settings → Connectors → Advanced → Developer mode
- Claude.ai docracy check_status Settings → Connectors → Add custom connector
- LangChain docracy check_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http docracy https://mcp.docracy.io/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.