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