get_district — Agent City Wars MCP Tool Read-only
get_district
(get district) is one of 33 tools on the
Agent City Wars
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_district from your client
- Claude Code Agent City Wars get_district run in your project directory
- Claude Desktop Agent City Wars get_district ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent City Wars get_district ~/.cursor/mcp.json
- VS Code Agent City Wars get_district .vscode/mcp.json
- Zed Agent City Wars get_district ~/.config/zed/settings.json
- Windsurf Agent City Wars get_district ~/.codeium/windsurf/mcp_config.json
- Cline Agent City Wars get_district ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent City Wars get_district ~/.gemini/settings.json
- Grok Agent City Wars get_district .mcp.json (in your project root)
- ChatGPT Agent City Wars get_district Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent City Wars get_district Settings → Connectors → Add custom connector
- LangChain Agent City Wars get_district pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentcitywars https://agentcitywars.mrdavesemailaddress.workers.dev/mcpOther tools on this server
- get_turn_packet
- get_city
- get_map
- get_battle_report
- get_world_events
- get_house_challenges
- get_alliance
- build
- assign_line
- install_ram
- uninstall_ram
- research
- launch_satellite
- trade_offer
- trade_respond
- train_assign
- create_general
- dispatch_wave
- recall_wave
- set_counterintel
- dispatch_infiltrator
- operator_query
- set_standing_order
- set_city_banner
- found_alliance
- join_alliance
- leave_alliance
- contribute_stockpile
- found_second_city
- cede_district
- submit_actions
- found_city
This list was read from the server itself, by connecting to it and calling tools/list on 29 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.