Connect Your Client

Wire Trade Echo MCP into Cursor IDE, native Grok Bot, grok.com, Grok CLI, Claude, ChatGPT, Meta Muse, and Codex.

MCP URL:

https://api.tradeecho.com/api/mcp/intel

Replace te_live_YOUR_TOKEN with the PAT from Agent Connections.

The server speaks stateless JSON-RPC over HTTP POST (JSON responses, no SSE stream, no session id). In clients that ask for a transport type, pick HTTP / Streamable HTTP, not SSE or stdio.

Free plan#

A free Trade Echo account can connect from any client that signs in to Trade Echo (grok.com, Grok Bot, Claude, ChatGPT, Meta Muse and others). Personal access tokens need a paid plan, so token setups (Cursor IDE, Grok CLI, Claude Code with a PAT) do not work on the free plan. The consent screen shows the free plan instead of the usual scopes: no My Account switch, no Trading section.

Two tools: get_daily_echo_brief (SPX levels and GEX Rating from the morning edition) and get_morning_levels (SPY and QQQ).
3 briefs a day, reset at 12:00 AM ET. GEX Rating describes the volatility regime, not market direction.
One free connection at a time. Connecting again, from the same client or another one, replaces the old connection.
Every other tool needs a paid plan. On the free plan, those tools answer with a link to plans.

Cursor IDE#

PAT via mcp.json headers. Native Grok Bot in Cursor uses OAuth (next section), not this PAT.

Add to MCP settings (JSON), or use Cursor's MCP UI and paste equivalent fields:

{
  "mcpServers": {
    "trade-echo": {
      "url": "https://api.tradeecho.com/api/mcp/intel",
      "headers": {
        "Authorization": "Bearer te_live_YOUR_TOKEN"
      }
    }
  }
}

Then ask Cursor something like: "Using Trade Echo, show unusual call flow on NVDA today."

Grok Bot#

Full guide: tradeecho.com/mcp/grok

Native Grok Bot uses OAuth. No PAT and no Bearer header.

Ask Grok Bot to connect Trade Echo MCP, or add a custom MCP connector with:
```
https://api.tradeecho.com/api/mcp/intel
```
Click Connect. The client shows an OAuth link.
Follow the OAuth link. Sign in to Trade Echo, accept the terms, click Allow.
Tools work - ask for flow, dealer levels, Discovery noteworthy prints, or session structure (VWAP / ORB).

Account tools (get_my_broker_snapshot, journal, copy status) appear only if you checked My Account on the consent page.

Grok Bot signs in with OAuth, so there is no token to paste. The connection shows on Agent Connections as type oauth. Revoke anytime.

grok.com#

Same MCP URL and Trade Echo consent as native Grok Bot. Add a custom MCP connector, paste https://api.tradeecho.com/api/mcp/intel, connect, follow the OAuth link, sign in, click Allow. No PAT.

Grok CLI#

grok mcp add --transport http trade-echo https://api.tradeecho.com/api/mcp/intel \
  --header "Authorization: Bearer te_live_YOUR_TOKEN"

Claude.ai / Claude Desktop Connectors#

Full guide: tradeecho.com/mcp/claude

Claude's custom connectors use OAuth (Settings → Connectors). They do not take a PAT in the connector UI:

Open Settings → Connectors → Add custom connector (claude.ai web or Claude Desktop).

Paste the MCP URL:

https://api.tradeecho.com/api/mcp/intel

Click Add, then Connect. Follow the OAuth link, sign in, accept the terms, click Allow.
Ask Claude for flow, dealer levels, or a futures session brief.

The connection shows on Agent Connections as type oauth. Revoke anytime.

Optional: Claude Desktop can instead use a local MCP JSON config with an Authorization: Bearer PAT header, same as Cursor IDE.

Claude Code#

With a PAT:

claude mcp add trade-echo \
  --transport http \
  https://api.tradeecho.com/api/mcp/intel \
  --header "Authorization: Bearer te_live_YOUR_TOKEN"

Or with OAuth: add the server without the --header line, then run /mcp inside Claude Code and choose Authenticate.

Codex#

codex mcp add trade-echo --url https://api.tradeecho.com/api/mcp/intel

Set the bearer token in MCP settings, or:

export TRADE_ECHO_MCP_PAT="te_live_YOUR_TOKEN"

Point bearer_token_env_var at TRADE_ECHO_MCP_PAT if your Codex MCP config supports it.

ChatGPT#

Full guide: tradeecho.com/mcp/chatgpt

OAuth - no PAT.

In ChatGPT, open Settings → Apps & connectors (or Plugins) and enable Developer mode.

Add a custom MCP app and paste:

https://api.tradeecho.com/api/mcp/intel

ChatGPT shows an OAuth link. Follow it, sign in to Trade Echo, accept the terms, click Allow.
Ask ChatGPT to use Trade Echo MCP for flow or dealer levels.

The connection shows on Agent Connections as type oauth. Revoke anytime.

Meta Muse#

Full guide: tradeecho.com/mcp/meta-muse

Muse builds a custom connector for Trade Echo itself. You tell it where the server is, and it handles the setup.

In Muse, ask:

Connect Trade Echo using the MCP server at https://api.tradeecho.com/api/mcp/intel. If you need a Client ID, use trade-echo-mcp.

Sign in when Muse asks. You have two options:
- OAuth: follow the sign-in link, sign in to Trade Echo, accept the terms, and click Allow. If Muse asks for a Client ID, enter trade-echo-mcp exactly. It is not your email or username.
- PAT: create a token on Agent Connections. Enter it only in Muse's secure credential prompt. Never paste it into the chat.
Ask Muse for flow, dealer levels, dark pool prints, or a futures session brief.

The connection shows on Agent Connections as Muse. You can revoke it anytime. Your Muse login and your Trade Echo login don't need to use the same email.

Muse Code#

Add Trade Echo to ~/.config/muse/settings.json:

{
  "schema_version": 1,
  "mcp_servers": {
    "trade-echo": {
      "transport": "streamable_http",
      "url": "https://api.tradeecho.com/api/mcp/intel",
      "headers": { "Authorization": "Bearer te_live_YOUR_TOKEN" }
    }
  }
}

Verify the connection#

In any connected agent, ask:

List Trade Echo MCP tools.

You should see tools such as get_option_flow, get_noteworthy_flow (Discovery noteworthy prints), get_breaking_news (Discovery Breaking News tab), get_session_structure, get_dealer_edge_data, get_dark_pool_data, and get_futures_session_levels, depending on the scopes you granted. Journal and holdings tools appear only with My Account.

If you get 401 Unauthorized:

Token missing, mistyped, or revoked
OAuth was never completed (Connect shown, but consent / Allow not finished)
Wrong header format (Authorization: Bearer te_live_...)

If you get 403 subscription_inactive:

Your Trade Echo membership is not active. Renew at tradeecho.com/pricing; the same connection works again once it is.

If you get credit limit errors:

Wait for the hourly reset, or buy bonus credits on Agent Connections