get_my_digest — DevStackPulse MCP Tool Read-only
get_my_digest
(get my digest) is one of 3 tools on the
DevStackPulse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_my_digest from your client
- Claude Code DevStackPulse get_my_digest run in your project directory
- Claude Desktop DevStackPulse get_my_digest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DevStackPulse get_my_digest ~/.cursor/mcp.json
- VS Code DevStackPulse get_my_digest .vscode/mcp.json
- Zed DevStackPulse get_my_digest ~/.config/zed/settings.json
- Windsurf DevStackPulse get_my_digest ~/.codeium/windsurf/mcp_config.json
- Cline DevStackPulse get_my_digest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DevStackPulse get_my_digest ~/.gemini/settings.json
- Grok DevStackPulse get_my_digest .mcp.json (in your project root)
- ChatGPT DevStackPulse get_my_digest Settings → Connectors → Advanced → Developer mode
- Claude.ai DevStackPulse get_my_digest Settings → Connectors → Add custom connector
- LangChain DevStackPulse get_my_digest pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http devstackpulse https://stackpulse-mcp.onrender.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 October 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.