MCP server
The AllenHark MCP server lets an AI client, such as Claude, ChatGPT, Cursor or Codex, work with AllenHark for you. It is a remote server on the MCP Streamable HTTP transport, at:
https://mcp.allenhark.com/mcpThe public tools are live now and need no sign-in. The account tools arrive with the switch to the new AllenHark platform; until then there is nothing to sign in to.
The server holds no keys and makes no decisions of its own. Every account call goes to the AllenHark account API as you, so the same ownership rules, limits and checks apply as in the console.
What it can do
- Without signing in (live now): search and read the docs, list products, prices and endpoints, write connection code for RPC, gRPC, shreds and Relay, build and explain Yellowstone gRPC subscribe requests, estimate priority fees, and decode transactions.
- After you sign in (with the platform switch): your account, subscriptions and renewal dates, usage, connection checks, your bots' PnL, positions and trades, settings analysis with replays of past launches, your VPS servers and a one-time console link, your alert rules, and support tickets.
- With the scopes you grant: buy or renew a subscription through a payment link, control your bots, manage keys and access, and set alert rules. See Scopes.
Replays run on past launches only, and every replay result says so: "Replayed on past launches, not a forecast."
Decoding transactions
decode_transaction takes a signature, which it looks up on the public RPC, or the raw transaction in base64 or base58. It reads legacy, v0 and v1 transactions, including accounts loaded from lookup tables, and returns:
- every instruction by name, with its accounts named and its arguments decoded;
- inner instructions and Jito tips;
- SOL and token balance changes per owner;
- the fee, priority fee and compute units;
- the last log lines, and the error in plain words if it failed;
- a summary of what the fee payer bought or sold.
Instructions are decoded for System, Token, Token-2022, Associated Token Account, Compute Budget, Memo, Pump.fun, PumpSwap, Raydium AMM v4, CPMM, CLMM and LaunchLab, Meteora DLMM and DAMM v2, Orca Whirlpool and Jupiter. Other programs are named where known, with their arguments left undecoded. Some arguments are not decoded yet: Token-2022 extensions, Raydium AMM v4 instructions other than swaps, and the steps inside a Jupiter route, of which only the count is shown.
decode_instruction decodes one instruction from its program id and data, with its accounts if you have them. For an unknown program it gives the discriminator and the data length.
Connect your client
Add the server URL to your client. Each section below gives the exact config for that client and how it signs in. There are two ways to sign in, and neither puts a token in the chat:
- Browser sign-in. The client opens the AllenHark console in your browser when a tool needs your account. Most clients do this on their own.
- An MCP token. For clients without browser sign-in, and for headless agents, create an
ahm_token in the console and put it in the client's config as the headerAuthorization: Bearer ahm_….
Without either, the public tools still work. Replace ahm_your_token below with your token, or leave the header out to use the public tools only.
Claude Code
claude mcp add --transport http allenhark https://mcp.allenhark.com/mcpRun /mcp inside Claude Code and choose AllenHark to sign in in the browser. To use a token instead:
claude mcp add --transport http allenhark https://mcp.allenhark.com/mcp --header "Authorization: Bearer ahm_your_token"In a project's .mcp.json, ${VAR} reads the token from the environment:
{
"mcpServers": {
"allenhark": {
"type": "http",
"url": "https://mcp.allenhark.com/mcp",
"headers": { "Authorization": "Bearer ${ALLENHARK_MCP_TOKEN}" }
}
}
}Claude.ai
Open Customize, then Connectors, and choose Add custom connector. Name it AllenHark and enter https://mcp.allenhark.com/mcp. On a Team or Enterprise plan, an owner adds the connector for the organisation first. Claude.ai signs in through the browser; it connects from Anthropic's servers and can't send your own token.
Claude Desktop
Add the connector the same way as on Claude.ai; it is shared with your Claude account and signs in through the browser. The claude_desktop_config.json file only starts local servers, so to use a token there, run the server through mcp-remote (Node 18 or later):
{
"mcpServers": {
"allenhark": {
"command": "npx",
"args": ["-y", "mcp-remote@latest", "https://mcp.allenhark.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer ahm_your_token" }
}
}
}Keep Authorization:${AUTH_HEADER} without spaces; some clients split arguments on spaces. Without the --header arguments, mcp-remote signs in through the browser itself. The same config works in any client that only starts local servers.
ChatGPT
On chatgpt.com, open Plugins, choose + and then Add custom MCP server. Enter AllenHark and https://mcp.allenhark.com/mcp. Until the platform switch, choose no authentication; after it, choose OAuth to sign in through the browser. ChatGPT can't send a token header.
The server has the search and fetch tools ChatGPT uses for deep research, over the AllenHark docs. ChatGPT asks before running a tool that isn't marked read-only; every public AllenHark tool is.
OpenAI Codex
codex mcp add allenhark --url https://mcp.allenhark.com/mcp
codex mcp login allenharkOr in ~/.codex/config.toml, with the token read from an environment variable instead of signing in:
[mcp_servers.allenhark]
url = "https://mcp.allenhark.com/mcp"
bearer_token_env_var = "ALLENHARK_MCP_TOKEN"Cursor
Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:
{
"mcpServers": {
"allenhark": {
"url": "https://mcp.allenhark.com/mcp"
}
}
}Cursor signs in through the browser. To use a token, add "headers": { "Authorization": "Bearer ${env:ALLENHARK_MCP_TOKEN}" } next to url.
VS Code with GitHub Copilot
Add to .vscode/mcp.json, or to your user mcp.json (MCP: Open User Configuration):
{
"servers": {
"allenhark": {
"type": "http",
"url": "https://mcp.allenhark.com/mcp"
}
}
}VS Code signs in through the browser. To use a token, it can ask for it once and keep it out of the file:
{
"inputs": [
{ "type": "promptString", "id": "allenhark-token", "description": "AllenHark MCP token", "password": true }
],
"servers": {
"allenhark": {
"type": "http",
"url": "https://mcp.allenhark.com/mcp",
"headers": { "Authorization": "Bearer ${input:allenhark-token}" }
}
}
}Copilot sends at most 128 tools per request across all your servers. Visual Studio reads the same servers format from .mcp.json in your solution or user folder.
Windsurf and Devin
devin mcp add allenhark https://mcp.allenhark.com/mcp
devin mcp login allenharkOr in ~/.config/devin/mcp_config.json:
{
"mcpServers": {
"allenhark": {
"url": "https://mcp.allenhark.com/mcp",
"transport": "http"
}
}
}OpenCode
In opencode.json, or ~/.config/opencode/opencode.json:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"allenhark": {
"type": "remote",
"url": "https://mcp.allenhark.com/mcp",
"enabled": true
}
}
}OpenCode signs in on its own, or with opencode mcp auth allenhark. To use a token, set "oauth": false and "headers": { "Authorization": "Bearer {env:ALLENHARK_MCP_TOKEN}" }. Kilo Code reads the same mcp block from kilo.jsonc.
Zed
In settings.json:
{
"context_servers": {
"allenhark": {
"url": "https://mcp.allenhark.com/mcp"
}
}
}Zed signs in through the browser when no Authorization header is set. To use a token, add "headers": { "Authorization": "Bearer ahm_your_token" }.
Cline
In cline_mcp_settings.json (MCP Servers, then Configure). Keep "type": "streamableHttp"; without it Cline uses an older transport.
{
"mcpServers": {
"allenhark": {
"type": "streamableHttp",
"url": "https://mcp.allenhark.com/mcp",
"headers": { "Authorization": "Bearer ahm_your_token" },
"disabled": false
}
}
}Roo Code
In .roo/mcp.json, or the global mcp_settings.json:
{
"mcpServers": {
"allenhark": {
"type": "streamable-http",
"url": "https://mcp.allenhark.com/mcp",
"headers": { "Authorization": "Bearer ahm_your_token" }
}
}
}Continue
In .continue/mcpServers/allenhark.yaml:
name: AllenHark
version: 0.0.1
schema: v1
mcpServers:
- name: allenhark
type: streamable-http
url: https://mcp.allenhark.com/mcp
requestOptions:
headers:
Authorization: Bearer ${{ secrets.ALLENHARK_MCP_TOKEN }}Gemini CLI
gemini mcp add --transport http allenhark https://mcp.allenhark.com/mcpOr in ~/.gemini/settings.json. Use httpUrl; the url key selects an older transport.
{
"mcpServers": {
"allenhark": {
"httpUrl": "https://mcp.allenhark.com/mcp"
}
}
}Gemini CLI signs in through the browser on its own, or with /mcp auth allenhark. To use a token, add "headers": { "Authorization": "Bearer ahm_your_token" }. Antigravity uses serverUrl instead of httpUrl, in ~/.gemini/config/mcp_config.json.
Goose
In ~/.config/goose/config.yaml:
extensions:
allenhark:
type: streamable_http
name: allenhark
enabled: true
uri: https://mcp.allenhark.com/mcp
timeout: 300Goose signs in through the browser on its own. To use a token, add headers with Authorization: "Bearer ahm_your_token".
Warp
Open Settings, then MCP Servers, choose + Add and paste:
{
"mcpServers": {
"allenhark": {
"url": "https://mcp.allenhark.com/mcp"
}
}
}Warp signs in through the browser. Warp's cloud agents can't, so give them a token with "headers": { "Authorization": "Bearer ahm_your_token" }.
JetBrains AI Assistant and Junie
In AI Assistant, open Settings, Tools, AI Assistant, Model Context Protocol and add a server with the same mcpServers JSON as Warp. Junie reads it from .junie/mcp/mcp.json and signs in with /mcp, then Authorize. For a token in AI Assistant, use the mcp-remote config from Claude Desktop.
Amazon Q Developer and Kiro
Q Developer CLI and Kiro take the server in mcpServers, in the Q agent config or .kiro/settings/mcp.json:
{
"mcpServers": {
"allenhark": {
"type": "http",
"url": "https://mcp.allenhark.com/mcp"
}
}
}Both sign in through the browser (in Q, run /mcp). In the Q Developer IDE plugin, add an HTTP server with the URL in the MCP panel.
LM Studio
In the Program tab, choose Install, then Edit mcp.json, and add the same mcpServers JSON as Warp, with "headers": { "Authorization": "Bearer ahm_your_token" } for your account.
Other clients
Any client that supports remote MCP servers over Streamable HTTP works with the URL above. A client that only starts local servers works through the mcp-remote config shown for Claude Desktop. Tool names, input schemas and descriptions are kept within the limits of the strictest clients, so no tool is dropped or renamed.
Signing in
Account tools come with the switch to the new AllenHark platform. From then on, when the client calls a tool that needs your account, the server answers that it needs a sign-in, and the client opens your browser on the AllenHark console.
- Sign in to the console the way you usually do.
- Read the consent screen: the client's name, the scopes it asks for, and the caps that will apply.
- Tick the scopes you want and approve. Only
readis ticked to begin with; every other scope is your choice and comes with a plain warning.
The client is then connected. It holds an access token that lasts 15 minutes and refreshes it on its own, so you sign in again only now and then, not in the middle of a conversation.
Clients that can't open a browser, such as headless agents, CI or an SSH session, and clients without browser sign-in, use an MCP token instead: create one in the console, give it a name, scopes and an expiry (90 days unless you choose otherwise), and put it in the client's config as Authorization: Bearer ahm_…. It is shown once. Never paste it into the chat.
Every connection, whichever way it was made, is listed in the console under Connected apps with its client, scopes, when it was created and when it was last used. Revoking one cuts it off at its next call.
Scopes
| Scope | What the client may do |
|---|---|
read | Read your account, products, usage, payments, bots, VPS servers and alert rules; run settings analysis and replays; open and read support tickets; get a VPS console link |
billing | Create a checkout order and give you its payment link. It can't pay, change a payment method or cancel anything |
bots.control | Pause and resume buying, pause all, stop without selling, change a bot's strategy, roll it back, set its schedule and launchpads, reset practice balance and run maintenance tasks |
bots.trade | Manual buy and sell, close a position, and stop and sell all |
bots.live | Ask to move a bot from practice to live. You approve it in the console |
bots.withdraw | Ask to withdraw SOL to a saved address, and to add or remove withdraw addresses. You approve each one in the console |
relay.send | Simulate a transaction you signed yourself. The client never sends it |
products.manage | Create, rotate and revoke product keys, and switch a subscription between IP allowlist, API key or either |
vps.power | Start, stop and reboot a VPS |
alerts | Create, change and delete alert rules. Rules only notify you; they never trade or stop a bot |
Some of these actions are not open to AI clients yet and answer that you should use the console: simulating a transaction, VPS power, shred destinations, Jito pubkeys and the gRPC connection split.
Keys are shown to you, never to the client
When the client creates or rotates a product key, it gets no key. It gets a link to your console instead. You open it signed in to your account and see the key once. The link works once and expires after 10 minutes.
Never through the MCP
Whatever scopes you grant, these stay in the console: your AI limits, approving actions and entering your PIN, changing your PIN, linking alert channels, IP allowlists, support access to your bot servers, SSH keys on bot servers, importing or exporting a wallet, reinstalling or terminating a VPS and its root credentials, payment methods, deleting the account and changing its email.
Money safety
These rules apply to every tool that moves SOL or can cut off production traffic. The AllenHark platform enforces them, not the client.
Preview, then confirm
A money tool never acts on its first call. It first returns a preview: what will happen (the token, the side, the amount in SOL and in tokens, the estimated price and slippage, the fees and the position afterwards) and how much of your caps you have used today. The client shows you the preview, and only a second, separate call confirms it.
The preview is single-use, expires after 60 seconds, and is bound to that connection, that deployment and those exact parameters. A confirm with changed parameters, after expiry or a second time is refused. If a client retries a confirm, you get the first result again; the trade doesn't happen twice.
Limits you set
In the console you set your AI limits:
- a SOL limit per trade, and per day, for buys made through the MCP;
- a daily limit for SOL withdrawn through the MCP;
- the deployments and wallets the MCP may touch.
The highest limits you can set are 50 SOL per trade, 200 SOL of buys per day and 200 SOL withdrawn per day. A higher value is saved as the maximum. Days start at 00:00 UTC. Sells and closes don't count toward the limits.
No trade or withdrawal works through the MCP until you have set your limits. An action over a limit is refused; it is not sent to you for approval. The limits are checked at the preview and again at the confirm.
Your AI limits can only be changed in the console, signed in as yourself. An AI client can't change them, whatever scopes it holds.
Your PIN never goes in the chat
Going live, withdrawing, and adding or removing a withdraw address finish outside the chat. The confirm sends an approval link to your account email, and to Telegram or Discord if you have linked them. You open it in the console and enter your PIN there. The link expires after 10 minutes. Your limits are checked once more when you approve. Until then the client can only tell you the action is awaiting approval. You can also reject it, which needs no PIN.
You are told about every action
Every confirmed trade, go-live, withdrawal and address change made through the MCP goes to your alert channels, naming the client and what it did, with a reminder that you can revoke it under Connected apps. A strategy change to a live bot is notified the same way.
The bot's history shows these actions as made by the client "via MCP", or "via MCP, approved by you" for an action you approved in the console.
Turning it off
You can revoke a connection, or switch off MCP money scopes for the whole account, in one click in the console. AllenHark can also switch off money tools for every account at once.
Payment links
With billing, the client can quote a plan and create an order, and gives you a link of the form https://allenhark.com/checkout/pay/<order>. You open it, sign in if needed and pay from your own wallet. The same link is also emailed to you, so you can check that a link shown in the chat came from AllenHark. The MCP never sees a wallet or a card, and can't pay. Bot plans are monthly.
VPS console link
With read, the client can give you a link that opens one of your VPS servers' console in the browser on allenhark.com. You open it signed in to your AllenHark account. The link works once and expires after 5 minutes. No password or root credential is ever returned to the client.
Support tickets
With read, the client can open a support ticket for you and list your tickets with their status. A ticket has a subject, a message and, if you like, the product it is about. The client can attach your subscription state, connection checks and service status; keys, tokens, private keys and PINs are removed from everything it sends. AllenHark staff answer in the ticket, and you can read the answers through the client or in the console.
An account can have at most 3 open tickets at a time, counting tickets opened on Discord, in the console and through the MCP.
Alert rules
With alerts, the client can create, change and delete rules that tell you when something happens. A rule only sends you a message; it never trades or stops a bot. The kinds are:
- a bot's loss today goes over an amount of SOL;
- a bot stops or is halted;
- a bot wallet drops below an amount of SOL;
- a subscription or bot plan ends within a number of days;
- AllenHark posts an incident on a product and region you use.
Each rule goes to one linked channel: Telegram, a Discord DM or a Discord webhook. A rule sends at most once an hour, or once a day for a subscription ending. An account can have up to 50 rules. With read, the client can list your rules and when each last sent.
The wallet balance rule is saved but doesn't send yet: AllenHark doesn't receive your bot wallet balances yet.
Rate limits
Each signed-in connection can make 10 tool calls a second, with bursts of up to 30. Calls without sign-in share 3 a second per IP address, with bursts of up to 10. Over the limit, the tool answers with how many seconds to wait. In front of the server, each IP address can also send up to 20 requests a second, with bursts of up to 60.
