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