Elfa MCP
Model Context Protocol server for the Elfa API — crypto social intelligence from X and Telegram, API v3 events, positions and rankings across crypto and equities, plus Auto, a condition engine that watches the market and fires an action when your conditions are met.
Works with any MCP client, either signed in to the hosted server or running locally with an API key.
Install
Hosted, sign in with Elfa
Add https://mcp.elfa.ai/mcp as a remote MCP server in your client and approve it in your browser with your dev.elfa.ai account. No key to copy, nothing to install. If your client cannot sign in, run the server locally instead. Setup steps are in the MCP guide.
Local, API key
Get an API key at dev.elfa.ai. No install step — npx fetches the server on demand.
One click

Claude Desktop
Download elfa-mcp-<version>.mcpb from the latest release and open it. Claude Desktop installs it, prompts for your API key, and keeps it updated. Nothing else to configure.
Claude Code
claude mcp add elfa --env ELFA_API_KEY=your-key -- npx -y @elfa-ai/mcp
Cursor, VS Code, Claude Desktop, and other clients
{
"mcpServers": {
"elfa": {
"command": "npx",
"args": ["-y", "@elfa-ai/mcp"],
"env": {
"ELFA_API_KEY": "your-key"
}
}
}
}
VS Code uses "servers" instead of "mcpServers". Everything else is the same.
Ask "what's trending in crypto right now?" to confirm it works.
Configuration
| Variable | Required | Purpose |
|---|
ELFA_API_KEY | yes | Authenticates every request |
ELFA_TIMEOUT | no | Request timeout in ms, default 120000 |
ELFA_RETRIES | no | Retries on failure, default 0 |
ELFA_MCP_MAX_RESPONSE_CHARS | no | Response size ceiling, default 60000 |
ELFA_EXTRA_HEADERS | no | JSON object of extra headers to send upstream, for proxies and non-production environments |
Upstream requests identify themselves as User-Agent: elfa-mcp/<version> (<transport>; client=<app>). On stdio, <app> is the MCP client's name and version from the handshake; over HTTP, it is the connecting client's own User-Agent header. Set User-Agent in ELFA_EXTRA_HEADERS to send your own instead.
The timeout is high and retries are off on purpose. The interpretation endpoints are LLM-backed and can take over a minute, and they cost credits per attempt, so a silent retry would bill you again for a call you never saw. Raise ELFA_RETRIES only if you are calling the cheap measurement endpoints.
Some MCP clients apply their own timeout, often around 60 seconds. narratives and market_chat can exceed that; the request still completes and is still charged, even if the client gives up first.
Tools
16 tools, mapped to every documented /v2 and /v3 operation.
| Tool | Mode | Cost | What it does |
|---|
api_status | read | Free | Check API key tier, credit usage and remaining requests, and historyFrom, how far back events, market and calls read. Also confirms the API is reachable. |
mentions | read | 1 per call | Social mentions from X and Telegram. mode=top ranks a ticker's mentions by engagement, mode=search filters by keyword or account, mode=news returns the token news feed, which is X posts from accounts tagged as news sources rather than articles from news outlets. |
trending | read | 1 per call | What is gaining social attention. scope=tokens for tickers, scope=contracts_twitter or scope=contracts_telegram for contract addresses. |
narratives | read | 5 per call | Written narrative analysis with source links. scope=market extracts market-wide narratives, scope=keywords summarises events for specific keywords. |
account_stats | read | 1 per call | Smart follower and engagement stats for an X account. Legacy: it still works, but will be removed on 28 October 2026. |
market_chat | read | Varies by speed | Ask for written market analysis. Supports conversational chat, macro overview, quick summary, token intro, token analysis and account analysis. |
auto_build | read | 1 plus LLM usage | Turn a plain-language monitoring request into an EQL query. Returns a draft to validate and activate, it does not activate anything itself. |
auto_validate | read | Free | Check EQL syntax and get a cost estimate before activating, or check that a symbol has market data on a venue. |
auto_query | read | Free | Read side of Auto: list queries, poll one query, and read its executions and LLM sessions. |
auto_query_write | write | 5 plus LLM usage to create, free to cancel or delete | Activate, cancel or delete an Auto query. Activated queries run unattended and fire their action when conditions are met. |
auto_draft | write | Free, except convert which costs the same as creating a query | Manage inactive Auto drafts. Drafts do not evaluate until converted into an active query. |
entities | read | Free on PAYG and Grow until 31 Oct 2026 | Resolve a ticker, $cashtag, name, @handle, contract address, CoinGecko id, FIGI or CIK to the entity id that events and calls take. Matches exactly, it is not a search. |
events | read | Free on PAYG and Grow until 31 Oct 2026 | What is happening in crypto and equity markets. level=events for what happened and how prices reacted, level=storylines for one development threaded over days, level=arcs for storylines grouped into a larger movement. Searchable by topic. |
market | read | Free on PAYG and Grow until 31 Oct 2026 | Whole-market views for crypto or equities. view=mindshare ranks assets by share of attention, view=call_book is the crowd's long/short lean hour by hour, view=trending_contracts ranks contract addresses by how many posts pasted them. |
calls | read | Free on PAYG and Grow until 31 Oct 2026 | Positions accounts take in posts. level=calls for each post that takes or changes a position, level=episodes for each position from open to close with the author's track record, level=positioning for open longs and shorts on one asset now. |
top_accounts | read | Free on PAYG and Grow until 31 Oct 2026 | X accounts ranked by standing (how much other accounts engage with them) or, with metric, by their track record as callers (alphaScore, hitRate, avgReturn). |
Not exposed as tools:
chat-stream-v2 — A tool call returns one result, so streaming adds nothing. market_chat covers the same analysis.
auto-stream-queries-v2 — Long lived streams have no tool equivalent. Poll with auto_query.
auto-stream-query-v2 — Long lived streams have no tool equivalent. Poll with auto_query.
Some tools depend on the plan: today market_chat and the API v3 tools, which need a higher-tier plan than the free one. At startup (stdio) or per request (HTTP, cached for a minute per key), the server reads the key's scopes from /v2/key-status. A tool the plan doesn't include stays listed, but its description says it needs a higher-tier plan, and calling it returns the upgrade link without calling the API or spending credits. If the scopes can't be read within 3 seconds, every tool is listed as usual and the API decides.
Streaming endpoints stay available through the SDKs for applications that can consume SSE.
API v3
entities, events, market, calls and top_accounts read API v3: events, storylines and arcs; call books, mindshare and trending contracts; calls, call episodes and positioning; ranked accounts. They cover crypto and equities, are free on Pay-as-you-go and Grow plans until 31 October 2026, and are open to Enterprise keys.
- Filters take entity ids, not tickers. Resolve an asset with
entities first and reuse the id.
- Times are unix seconds. Milliseconds are refused.
- How far back a key reads depends on its plan.
api_status returns it as historyFrom.
Where this differs from the raw API
The tools deliberately do not inherit every API default, because an agent pays for verbosity in context.
| API | Here | Why |
|---|
pageSize | 10 to 50 depending on endpoint, max 100 | 10 | Page through rather than pull everything |
limit on v3 tools | 10 or 50 depending on endpoint, max 30 or 200 | 10 | Page with cursor rather than pull everything |
speed on chat | expert | fast | Cheaper by default, ask for expert when depth matters |
| Mention fields | full record | high signal fields | Pass verbosity: "detailed" for the rest |
| Large responses | returned whole | trimmed to fit, with a note | Keeps one call from filling the context window |
Every value is still settable per call: pageSize accepts up to 100, and limit up to the endpoint's maximum.
Auto
Auto queries run unattended. Once armed, a query keeps evaluating and fires its action without asking again.
The flow is three steps:
auto_build — describe what to watch in plain language, get EQL back
auto_validate — check the syntax and get the credit cost
auto_query_write — activate it
Actions can notify you, call a webhook, message a Telegram bot, or run an LLM analysis.