get_status — DocuQueue MCP MCP Tool Read-only
get_status
(get status) is one of 12 tools on the
DocuQueue MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_status from your client
- Claude Code DocuQueue MCP get_status run in your project directory
- Claude Desktop DocuQueue MCP get_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DocuQueue MCP get_status ~/.cursor/mcp.json
- VS Code DocuQueue MCP get_status .vscode/mcp.json
- Zed DocuQueue MCP get_status ~/.config/zed/settings.json
- Windsurf DocuQueue MCP get_status ~/.codeium/windsurf/mcp_config.json
- Cline DocuQueue MCP get_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DocuQueue MCP get_status ~/.gemini/settings.json
- Grok DocuQueue MCP get_status .mcp.json (in your project root)
- ChatGPT DocuQueue MCP get_status Settings → Connectors → Advanced → Developer mode
- Claude.ai DocuQueue MCP get_status Settings → Connectors → Add custom connector
- LangChain DocuQueue MCP get_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http docuqueue-mcp https://docuqueue.com/mcp/sseOther 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.