
million
io.github.KelowsPublished by GitHub account Kelowsv1.0.0Updated Oct 24, 2026
Operate a self-hosted Solana whale tracker and copy-trading deck: positions, rules, token checks.
Overview
Lets an assistant read and operate a self-hosted Solana whale tracker and copy-trading deck: positions, decisions, rules, token checks and wallet analysis.
- What you can do
- A thin MCP layer over the local API of million, a self-hosted Solana whale tracker and copy-trading deck. Tools cover deck status, open and closed positions with PnL, the decision log, why a token was or was not bought, current trading rules, followed-wallet flows and holdings, token safety checks, finding a token's biggest buyers, importing wallets, wallet PnL analysis, and following or unfollowing wallets. It can also change some rule fields and returns the before and after values.
- When to use it
- Useful if you already run the million deck locally and want to query or adjust it conversationally, for example asking how the deck is doing, why it skipped a token, or which wallets to follow. Not useful without a running deck.
- Requirements
- Runs locally over stdio via npx (npm package million-mcp). The million deck must be running on the same machine; it needs Node 24 or nvm and a free Helius API key. The deck's API defaults to and can be changed with the MILLION_API environment variable. Desktop clients only.
Installation
In SourceWeft
- Open million in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
million-mcp
MCP server for million, the open-source, self-hosted Solana whale tracker and copy-trading deck. It lets Claude Desktop, Cursor, Claude Code, VS Code or any MCP client read and operate your deck: status, positions, why a token was or wasn't bought, trading rules, roster order flow, token safety checks and finding wallets worth following.
It's a thin layer over the deck's local API, so the deck has to be running on your machine. No keys pass through it, and no tool can switch paper trading to live.
1. Run the deck
That clones, installs and starts million at http://localhost:5173 (you need Node 24 or nvm, and a free Helius API key).
2. Add the server to your client
Claude Code
Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json) and most other clients:
VS Code (.vscode/mcp.json):
If the deck's API isn't on http://localhost:3001/api, set MILLION_API in the server's env.
Tools
find_token_buyers and analyze_wallet spend your Helius credits.
Ask things like
- "How's my deck doing?"
- "Why didn't it buy CATE?"
- "Find whales from this token and add the three most consistent ones."
- "Make it only trade when two different owners agree, 0.2 SOL per trade."
Experimental software, provided as is, not financial advice. MIT licensed.
Source: packages/million-mcp/README.md at commit c89ad07
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts