get_city_pulse — events MCP Tool Read-only
get_city_pulse
(get city pulse) is one of 30 tools on the
events
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_city_pulse from your client
- Claude Code events get_city_pulse run in your project directory
- Claude Desktop events get_city_pulse ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor events get_city_pulse ~/.cursor/mcp.json
- VS Code events get_city_pulse .vscode/mcp.json
- Zed events get_city_pulse ~/.config/zed/settings.json
- Windsurf events get_city_pulse ~/.codeium/windsurf/mcp_config.json
- Cline events get_city_pulse ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI events get_city_pulse ~/.gemini/settings.json
- Grok events get_city_pulse .mcp.json (in your project root)
- ChatGPT events get_city_pulse Settings → Connectors → Advanced → Developer mode
- Claude.ai events get_city_pulse Settings → Connectors → Add custom connector
- LangChain events get_city_pulse pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http events https://eventchat-events-mcp-production.up.railway.app/mcp
Other tools on this server
- get_preference_onboarding
- create_event_preference_profile
- save_event_preferences
- get_event_preferences
- delete_event_preferences
- record_event_feedback
- get_event_feedback_prompt
- get_event_search_followups
- list_cities
- find_scene_entities
- get_artist
- get_venue
- search_events
- recommend_events
- recommend_events_for_user
- plan_night
- get_daily_roundup
- get_artist_events
- get_artist_page
- get_event
- get_ticket_purchase_policy
- get_ticket_offers
- quote_ticket_order
- purchase_ticket_order
- get_taste_profile
- bin_event
- save_event
- add_to_dizko_plan
- create_event_calendar_file
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.