get_my_guide_state — Afrotech.guide MCP Tool Read-only
get_my_guide_state
(get my guide state) is one of 24 tools on the
Afrotech.guide
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_my_guide_state from your client
- Claude Code Afrotech.guide get_my_guide_state run in your project directory
- Claude Desktop Afrotech.guide get_my_guide_state ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Afrotech.guide get_my_guide_state ~/.cursor/mcp.json
- VS Code Afrotech.guide get_my_guide_state .vscode/mcp.json
- Zed Afrotech.guide get_my_guide_state ~/.config/zed/settings.json
- Windsurf Afrotech.guide get_my_guide_state ~/.codeium/windsurf/mcp_config.json
- Cline Afrotech.guide get_my_guide_state ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Afrotech.guide get_my_guide_state ~/.gemini/settings.json
- Grok Afrotech.guide get_my_guide_state .mcp.json (in your project root)
- ChatGPT Afrotech.guide get_my_guide_state Settings → Connectors → Advanced → Developer mode
- Claude.ai Afrotech.guide get_my_guide_state Settings → Connectors → Add custom connector
- LangChain Afrotech.guide get_my_guide_state pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http afrotech-guide https://afrotech.guide/mcp
Other tools on this server
- search_guide
- search_jobs
- recommend_jobs
- get_job_context
- plan_career_day
- set_job_status
- search_events
- search_sessions
- search_people
- search_companies
- search_food
- get_guide_item
- get_conference_info
- plan_day
- plan_conference_week
- compare_guide_items
- find_networking_targets
- show_intro_messages
- update_my_guide_preferences
- save_guide_item
- remove_saved_guide_item
- save_itinerary
- delete_itinerary
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.