MCP

MCP (Model Context Protocol) lets an AI assistant call tools on a server you choose. This page shows how to connect one to Terminal and what it can do there.

The address is https://terminal.tokensmarketcap.com/mcp. Sign-in from an AI assistant works only on this address.

What MCP gives your assistant

Your assistant can read your alert rules, your alerts, and what the price did after each one. It can look up a coin's move and preview how often a condition would have been met.

It can also prepare a new rule, a change or quiet hours. Nothing changes until you agree. Every price it gets comes with its source and its time.

There are two ways to connect. You can sign in from the assistant, and Terminal asks you what it may do. Or you can send an API key, from software that supports one. Read Agents and API keys for keys and caps.

Connect Claude

For Claude.ai and Claude Desktop:

Add a custom connector in Claude with the address above.
Sign in to Terminal when Claude asks.
Terminal lists what Claude may do. Untick anything you do not want, then press Allow.

The full walk is in Claude.

Connect Claude Code

This command adds Terminal's server to Claude Code:

claude mcp add --transport http terminal https://terminal.tokensmarketcap.com/mcp

Run the command above in a terminal.
Run claude mcp login terminal, or type /mcp in a session and choose terminal.
Your browser opens Terminal. Choose what Claude Code may do, then press Allow.

To use an API key instead, follow Claude Code with an API key.

Connect ChatGPT

Add Terminal to ChatGPT as a connector, with the address above.
Sign in to Terminal when ChatGPT asks. ChatGPT does not send API keys.
Terminal lists what ChatGPT may do. Untick anything you do not want, then press Allow.

The full walk is in ChatGPT.

Agent frameworks

An agent built with the OpenAI Agents SDK, LangChain or CrewAI connects with an API key:

Create a key at API keys. The key needs the read scope.
Put the key in TERMINAL_API_KEY. Never put it in a URL.
Download the example for your framework and run it.

The examples and their settings are in Agent frameworks.

Tools

These are the tools your assistant can see. Tools that need sign-in also work with an API key. Some tools appear only when that part of Terminal is open to your account.

Tool	What it does	Needs sign-in
get_scoreboard	Public summary of what prices did after alerts of each kind, with sample sizes. No account needed.	No
get_shared_alert	One alert its owner shared publicly: the event, the price with its source and time, and the later prices. Pass the link or its 22-character code.	No
get_methodology	How Terminal gets prices, checks alerts, measures an unusual move, writes a note and records later prices. Without a page, lists the pages.	No
list_rules	The person's alert rules with their conditions and state.	Yes
get_rule	One alert rule: condition, wait between alerts, status and state per coin.	Yes
get_rule_record	The alerts of one rule and what the price did 1 hour, 4 hours, 24 hours and 7 days after each.	Yes
list_recent_alerts	Alerts the person's rules recorded since a time, newest first, with prices, sources and times.	Yes
get_alert	One recorded alert with its numbers, note and later prices, and the facts the note was written from.	Yes
get_delivery_status	Quiet hours, the person's destinations, and how a rule's latest alert was delivered.	Yes
get_move_facts	A coin's latest price and its change over a window, with volume against its 20-day average, its usual range, and Bitcoin over the same window.	Yes
get_price_range	A coin's highest and lowest price over a window, with their times, and the largest 5-minute change.	Yes
get_watchlist_moves	Each watchlist coin's change over a window next to its usual range.	Yes
search_assets	Coins Terminal has a price feed for, by name or ticker.	Yes
get_account	The person's plan, limits, API use this month and credits.	Yes
preview_rule	How often a condition would have been met over the last 30 days, and the price 1 hour and 24 hours after each time. A backtest: hypothetical, not a forecast. May use credits.	Yes
explain_move	A short note on a coin's move over a window, written from measured facts, with the facts as fields. Marked AI-written. May use credits.	Yes
propose_rule	Prepares a new alert rule with a 30-day preview and returns a summary and a token. Saves nothing.	Yes
propose_edit	Prepares a change to one alert rule and returns a summary and a token. Saves nothing.	Yes
propose_state	Prepares a pause, resume, snooze, mute or delete of one alert rule, and returns a summary and a token. Saves nothing.	Yes
propose_quiet_hours	Prepares turning quiet hours on for given times, or off. Saves nothing.	Yes
confirm_proposal	Makes the change a propose tool prepared. Call it only after the person agreed to that summary in this conversation.	Yes
cancel_proposal	Discards a prepared change.	Yes

Each call with sign-in or a key counts as one API call. preview_rule and explain_move can also spend credits. MCP for developers lists what each tool costs.

What needs your confirmation

Your assistant cannot change your account in one step. A change takes two tools, and you decide in between.

Propose. propose_rule, propose_edit, propose_state and propose_quiet_hours each prepare a change. They save nothing. Each returns a summary and a token.
You agree. Your assistant shows you the summary. Read it before you answer.
Confirm. confirm_proposal makes the change that was prepared. Terminal tells the assistant to call it only after you agreed to that summary in the conversation.
Cancel. cancel_proposal discards a prepared change.

Many apps also ask you before they run confirm_proposal, because it changes your account. These tools need the rules:write scope, shown as Create and change alerts.

To stop an assistant, revoke it under Connected apps on API keys. Its next call is refused.

Updated Oct 24, 2026