Skip to content

Claude.ai EventTrader MCP launchpad_launch_token

How to: Claude.ai EventTrader MCP launchpad_launch_token

client:Claude.ai transport:streamable-http tool:launchpad_launch_token

Add EventTrader MCP to Claude.ai

  1. 01

    Open Settings → Connectors → Add custom connector and merge this in. Keep any servers already there.

https://cymetica.com/mcp/v1
  1. 02

    Save the file and restart Claude.ai.

  2. 03

    Ask for something launchpad_launch_token does. Claude.ai lists the server's tools on connect and calls launchpad_launch_token itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that EventTrader MCP's identifier in your config matches the one above exactly.

Claude on the web takes a remote URL and completes OAuth in the browser. For a packaged server use Claude Desktop or Claude Code instead. Claude.ai docs

Set these first

EventTrader MCP will not start until these are set, so launchpad_launch_token never becomes available.

  • EVENT_TRADER_API_KEY
  • EVENT_TRADER_API_URL

Same tool, other clients

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.