plan_conference_week — Afrotech.guide MCP Tool
plan_conference_week
(plan conference week) 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 plan_conference_week from your client
- Claude Code Afrotech.guide plan_conference_week run in your project directory
- Claude Desktop Afrotech.guide plan_conference_week ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Afrotech.guide plan_conference_week ~/.cursor/mcp.json
- VS Code Afrotech.guide plan_conference_week .vscode/mcp.json
- Zed Afrotech.guide plan_conference_week ~/.config/zed/settings.json
- Windsurf Afrotech.guide plan_conference_week ~/.codeium/windsurf/mcp_config.json
- Cline Afrotech.guide plan_conference_week ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Afrotech.guide plan_conference_week ~/.gemini/settings.json
- Grok Afrotech.guide plan_conference_week .mcp.json (in your project root)
- ChatGPT Afrotech.guide plan_conference_week Settings → Connectors → Advanced → Developer mode
- Claude.ai Afrotech.guide plan_conference_week Settings → Connectors → Add custom connector
- LangChain Afrotech.guide plan_conference_week pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http afrotech-guide https://afrotech.guide/mcpOther 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
- compare_guide_items
- find_networking_targets
- show_intro_messages
- get_my_guide_state
- 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.