get_page_history — GetCited MCP Tool Read-only
get_page_history
(get page history) is one of 29 tools on the
GetCited
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_page_history from your client
- Claude Code GetCited get_page_history run in your project directory
- Claude Desktop GetCited get_page_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GetCited get_page_history ~/.cursor/mcp.json
- VS Code GetCited get_page_history .vscode/mcp.json
- Zed GetCited get_page_history ~/.config/zed/settings.json
- Windsurf GetCited get_page_history ~/.codeium/windsurf/mcp_config.json
- Cline GetCited get_page_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GetCited get_page_history ~/.gemini/settings.json
- Grok GetCited get_page_history .mcp.json (in your project root)
- ChatGPT GetCited get_page_history Settings → Connectors → Advanced → Developer mode
- Claude.ai GetCited get_page_history Settings → Connectors → Add custom connector
- LangChain GetCited get_page_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://app.getcited.dev/api/mcp
Other tools on this server
- how_to_authenticate
- get_setup_status
- list_projects
- add_project
- remove_project
- get_site_health
- get_next_work
- list_actions
- get_action
- claim_action
- complete_action
- dismiss_action
- run_audit
- add_keywords
- list_keywords
- rank_history
- check_rankings
- add_geo_prompts
- geo_summary
- check_geo
- run_brain
- get_behavior_digest
- set_project_profile
- get_project_profile
- list_opportunities
- get_content_brief
- list_regressions
- get_page_profile
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.