pds_health — Taproot: AT Protocol MCP MCP Prompt

pds_health is one of 3 prompts on the Taproot: AT Protocol MCP MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke pds_health from your client

• Claude Code Taproot: AT Protocol MCP Prompt/pds_health run in your project directory
• Claude Desktop Taproot: AT Protocol MCP Prompt/pds_health ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Taproot: AT Protocol MCP Prompt/pds_health ~/.cursor/mcp.json
• VS Code Taproot: AT Protocol MCP Prompt/pds_health .vscode/mcp.json
• Zed Taproot: AT Protocol MCP Prompt/pds_health ~/.config/zed/settings.json
• Windsurf Taproot: AT Protocol MCP Prompt/pds_health ~/.codeium/windsurf/mcp_config.json
• Cline Taproot: AT Protocol MCP Prompt/pds_health ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Taproot: AT Protocol MCP Prompt/pds_health ~/.gemini/settings.json
• Grok Taproot: AT Protocol MCP Prompt/pds_health .mcp.json (in your project root)
• ChatGPT Taproot: AT Protocol MCP Prompt/pds_health Settings → Connectors → Advanced → Developer mode
• Claude.ai Taproot: AT Protocol MCP Prompt/pds_health Settings → Connectors → Add custom connector
• LangChain Taproot: AT Protocol MCP Prompt/pds_health pip install langchain-mcp-adapters

Other prompts on this server

• who_engaged
• account_audit

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.