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