list_my_sources — DevStackPulse MCP Tool Read-only
list_my_sources
(list my sources) 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 list_my_sources from your client
- Claude Code DevStackPulse list_my_sources run in your project directory
- Claude Desktop DevStackPulse list_my_sources ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DevStackPulse list_my_sources ~/.cursor/mcp.json
- VS Code DevStackPulse list_my_sources .vscode/mcp.json
- Zed DevStackPulse list_my_sources ~/.config/zed/settings.json
- Windsurf DevStackPulse list_my_sources ~/.codeium/windsurf/mcp_config.json
- Cline DevStackPulse list_my_sources ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DevStackPulse list_my_sources ~/.gemini/settings.json
- Grok DevStackPulse list_my_sources .mcp.json (in your project root)
- ChatGPT DevStackPulse list_my_sources Settings → Connectors → Advanced → Developer mode
- Claude.ai DevStackPulse list_my_sources Settings → Connectors → Add custom connector
- LangChain DevStackPulse list_my_sources 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.