Documentation index

MCP server

The AllenHark MCP server is coming soon. It is not live yet; this page describes how it will work, so you can plan for it.

It lets an AI client, such as Claude or Cursor, work with AllenHark for you: read the docs and write connection code, see your account and subscriptions, review your managed bots' settings, and, only if you allow it, act on your behalf. It is a remote server on the MCP Streamable HTTP transport, at:

Text

https://mcp.allenhark.com/mcp

The server holds no keys and makes no decisions of its own. Every 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: search the docs, list products, prices and endpoints, write connection code for RPC, gRPC, shreds and Relay, build and explain Yellowstone gRPC subscribe requests, and decode transactions.
After you sign in: your account, subscriptions and renewal dates, usage, connection checks, your bots' PnL, positions and trades, settings analysis with replays of past launches, and SolTrace.
With the scopes you grant: buy or renew a subscription through a payment link, control your bots, and manage keys and access. See Scopes.

Replays run on past launches only, and every replay result says so: "Replayed on past launches, not a forecast."

Connect your client

Add the server URL to your client. The first time it needs your account, the client opens your browser to sign in (see Signing in).

Claude Desktop

Open Settings, then Connectors, and choose Add custom connector. Name it AllenHark and enter https://mcp.allenhark.com/mcp.

Claude.ai

Open Settings, then Connectors, and choose Add custom connector with the same name and URL. On a Team or Enterprise plan, an owner adds the connector for the organisation first.

Claude Code

Terminal

claude mcp add --transport http allenhark https://mcp.allenhark.com/mcp

Then run /mcp inside Claude Code and choose AllenHark to sign in.

Cursor

Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

JSON

{
  "mcpServers": {
    "allenhark": {
      "url": "https://mcp.allenhark.com/mcp"
    }
  }
}

Signing in

You never copy a token by hand. 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 read is 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.

A client that can't open a browser, such as an agent on a server or an SSH session, gets a short code and the address allenhark.com/connect instead. Open it on any device, enter the code and approve the same consent screen.

Headless agents and CI can 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 send it as Authorization: Bearer ahm_…. It is shown once.

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 and SolTrace, and run settings analysis and replays
`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, and change a bot's strategy
`bots.trade`	Manual buy and sell, sell a holding, close a position, stop and sell all, and SolTrace trades and activation
`bots.live`	Move a bot from practice to live
`bots.withdraw`	Withdraw SOL, and add or remove withdraw addresses
`relay.send`	Send a transaction you signed yourself through Relay
`products.manage`	Create, rotate and revoke product keys, change the access mode and IP allowlists, shred destinations, Jito pubkeys and the gRPC connection split
`vps.power`	Start, stop and reboot a VPS
`alerts`	Set alert rules and channels. Rules only notify you; they never trade or stop a bot

The client never sees a full product key: a new key is shown to you once, in the browser, through a one-time link.

Never through the MCP

Whatever scopes you grant, these stay in the console: 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.

Caps you set

In the console you set:

a SOL limit per trade and per day for trades made through the MCP;
a daily withdrawal limit;
the deployments and wallets the MCP may touch.

No money scope works until you have set your caps.

Your PIN never goes in the chat

Going live, withdrawing, changing your PIN and changing withdraw addresses 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 works once and expires after 10 minutes. Until then the client can only tell you the action is awaiting approval.

New withdraw addresses wait 24 hours

An address added through the MCP is on hold for 24 hours. You are emailed at once and can cancel it from the email, and no withdrawal can use it during the hold. Removing an address takes effect at once.

You are told about every action

Every confirmed trade, go-live, withdrawal and address change made through the MCP goes to your alert channels and shows in the bot's history as made via MCP. A strategy change to a live bot is notified the same way.

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.