Skip to content

Quickstart

About a minute from zero to your assistant querying the publication.

1. Connect it

The simplest way in — no API key to copy or paste.

  1. In your AI assistant, open connector settings (Claude: Settings → Connectors → Add custom connector; ChatGPT: Settings → Connectors).
  2. Add the connector URL: 
    https://mcp.thecoindaily.co/mcp
  3. You'll be sent to a Coin Daily sign-in page to create a free account (email + password). Approve access — the tools now appear in your assistant.

That's the whole signup. See Authentication for what's happening under the hood, and the Claude / ChatGPT setup pages for client-specific notes.

Building your own agent or calling from a script?

Use a direct API key instead — see Authentication → API keys and Raw HTTP / curl.

2. Your first call

Ask your assistant something like:

"What does The Coin Daily's active market report say about the crypto market right now?"

This triggers get_active_market_report. The assistant receives a structured response — the market read, the key observations and tensions the desk is tracking, tone, and confidence — and surfaces it back with attribution.

Or, for a single asset:

"Pull The Coin Daily's brief on BTC-USD."

This calls get_ticker_brief: direction, conviction, key levels, recent developments, and cross-validation — stamped with the time of the read.

3. Verify it directly (optional)

To test without a client, hit the JSON-RPC endpoint with a direct API key:

export TCD_KEY="tcd_..."   # from Authentication → API keys

curl -X POST https://mcp.thecoindaily.co/mcp/ \
  -H "Authorization: Bearer $TCD_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \
  | jq '.result.tools[].name'

Should print twelve tool names. Note the trailing slash on /mcp/ — without it the server returns a 307 redirect that some HTTP clients don't follow on POST.

What you've got

A connection to a continuous editorial pipeline. Each call returns the publication's current read — not historical, not extrapolated, not your assistant's guess. Repeated calls within a refresh window return the same data (cached at source); after the next cycle it shifts to the latest analyst run.

Next steps