Cursor
Updated .
Cursor can read your alerts and propose changes through Terminal's MCP server. MCP (Model Context Protocol) lets an AI assistant call tools on a server you choose. Read MCP for the tools and what they cost.
The address is https://terminal.tokensmarketcap.com/mcp. Use this address. Sign-in works only on this host.
Add the server
Cursor reads MCP servers from .cursor/mcp.json in a project, or from ~/.cursor/mcp.json in your home directory for every project. Add terminal under mcpServers:
{
"mcpServers": {
"terminal": {
"url": "https://terminal.tokensmarketcap.com/mcp"
}
}
}
Sign in
Cursor's documentation says Cursor supports OAuth for servers that require it. It does not say where a server you added by hand starts its sign-in, so look for terminal in Cursor's MCP settings. When the sign-in starts, your browser opens Terminal. Sign in to Terminal first if it asks.
Terminal's page asks whether to allow the app to use your Terminal account, and lists what it may do. "Read alerts, rules and receipts" is always on. "Create and change alerts" lets Cursor propose changes for you to confirm. "Subscribe to services on the exchange" shows only if the exchange is open to your account. It starts unticked, because it spends credits. Untick anything you do not want, then press Allow.
Terminal's server follows the sign-in rules of the MCP specification. We have tested sign-in from Claude Code. We have not tested it from Cursor yet. If sign-in does not finish, use an API key.
With an API key
Create a key at API keys. Tick "Create and change alerts" when you create it if Cursor should propose changes. Every plan includes a key. Then send the key on the Authorization: Bearer header:
{
"mcpServers": {
"terminal": {
"url": "https://terminal.tokensmarketcap.com/mcp",
"headers": {
"Authorization": "Bearer ${env:TERMINAL_API_KEY}"
}
}
}
}
Cursor fills ${env:TERMINAL_API_KEY} from the environment variable of that name, so the key itself stays out of the file. Set the variable before you start Cursor. Do not put the key in the address. Each tool call counts as one API call for the key. Read Authentication for scopes and caps.
What the tools do
- Three tools read public pages and need no account:
get_scoreboard,get_shared_alertandget_methodology. - The read tools list your alert rules, your alerts, and what the price did after each one.
preview_ruleandexplain_movecan spend credits past what your plan includes. MCP gives the amounts.- To change anything, Cursor calls a propose tool and shows you a summary. Nothing changes until you agree in the conversation.
Terminal does not place trades, and neither do these tools.
What to ask
- "List my Terminal alerts."
- "What did the price do after my last SOL alert?"
- "Explain BTC's move over the last 4 hours." This uses
explain_move, which can spend credits. - "Pause my ETH alert." Cursor proposes the change and shows you a summary. Nothing changes until you agree.
Stop access
Open the API keys page in Settings. Under Connected apps, revoke Cursor. If you connected with a key, revoke the key on the same page. Then remove the terminal entry from the file you added it to.
Where these steps come from
The file names, the mcpServers entry, the headers field and the ${env:NAME} form are from Cursor's own documentation, Model Context Protocol (MCP), read on November 11, 2026. Cursor can change them. If a step here does not match what you see, follow Cursor's page.
All developer pages
Terminal reports market events for conditions you set. It does not tell you to buy, sell, or hold, and it does not place trades.