get_event_week_details — LONG Events MCP Tool Read-only
get_event_week_details
(get event week details) is one of 16 tools on the
LONG Events
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_event_week_details from your client
- Claude Code LONG Events get_event_week_details run in your project directory
- Claude Desktop LONG Events get_event_week_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LONG Events get_event_week_details ~/.cursor/mcp.json
- VS Code LONG Events get_event_week_details .vscode/mcp.json
- Zed LONG Events get_event_week_details ~/.config/zed/settings.json
- Windsurf LONG Events get_event_week_details ~/.codeium/windsurf/mcp_config.json
- Cline LONG Events get_event_week_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LONG Events get_event_week_details ~/.gemini/settings.json
- Grok LONG Events get_event_week_details .mcp.json (in your project root)
- ChatGPT LONG Events get_event_week_details Settings → Connectors → Advanced → Developer mode
- Claude.ai LONG Events get_event_week_details Settings → Connectors → Add custom connector
- LangChain LONG Events get_event_week_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http long-events https://belong.events/functions/v1/mcp-server/mcpOther tools on this server
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.