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