evo_activity_list — EVO Academia MCP Tool
evo_activity_list
(evo activity list) is one of 26 tools on the
EVO Academia
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call evo_activity_list from your client
- Claude Code EVO Academia evo_activity_list run in your project directory
- Claude Desktop EVO Academia evo_activity_list ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EVO Academia evo_activity_list ~/.cursor/mcp.json
- VS Code EVO Academia evo_activity_list .vscode/mcp.json
- Zed EVO Academia evo_activity_list ~/.config/zed/settings.json
- Windsurf EVO Academia evo_activity_list ~/.codeium/windsurf/mcp_config.json
- Cline EVO Academia evo_activity_list ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EVO Academia evo_activity_list ~/.gemini/settings.json
- Grok EVO Academia evo_activity_list .mcp.json (in your project root)
- ChatGPT EVO Academia evo_activity_list Settings → Connectors → Advanced → Developer mode
- Claude.ai EVO Academia evo_activity_list Settings → Connectors → Add custom connector
- LangChain EVO Academia evo_activity_list pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http evo-mcp https://api.mcp.ai/p_evoOther tools on this server
- evo_list_accounts
- evo_configuration
- evo_member_list
- evo_member_get
- evo_get_member_count
- evo_membership
- evo_entries
- evo_receivables
- evo_receivables_mark_received
- evo_sales
- evo_sales_create
- evo_prospect
- evo_prospect_write_create
- evo_prospect_write_update
- evo_activity_schedule
- evo_activity_write_enroll
- evo_activity_write_change_status
- evo_employees
- evo_bank_accounts
- show_version
- report_bug
- connect
- toolkit_info
- marketplace
- authenticate
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.