Skip to main content
The OrbitFlare MCP server exposes Shredstream-optimized Solana RPC, gRPC streaming, dedicated nodes, and validator infrastructure as tools your AI assistant can call directly. Each capability is its own tool with a focused input schema: no internal action routers, no result-id pagination dance.
Pair the MCP server with the Skill for the best experience. The skill teaches the agent how OrbitFlare works; the MCP server lets it actually call OrbitFlare without leaving the chat.

Install

Most hosts take the same JSON shape; only the file location differs:
Codex CLI uses TOML at ~/.codex/config.toml (or <project>/.codex/config.toml):

Get a license key

Sign up at orbitflare.com and copy your license key from the Licenses section of the dashboard. The Free plan gives you 10 RPS, enough to start building immediately. If you’d rather not put the key in the host config, leave the env var unset and call setApiKey from chat:
Set my OrbitFlare API key to xxxx-xxxx-xxxx.

Configuration

All values can be overridden at runtime via the setApiKey tool, which is handy when switching networks or pinning a region without restarting the host.

Regional endpoints

mainnet (auto-routed) is the default. To pin a region, call setApiKey with one of: ash, ny, la, slc, ams, fra, lon, dub, siau, tok, sgp.

Tools

53 tools, grouped by domain. Every tool is independently callable.

RPC reads

Account, profile, and plans

Auth (device code + wallet challenge)

API keys and licenses

Billing

Streaming, staking, swap

Wallet and write

Flows

Auth (device code)

1

Request a device code

requestDeviceCode returns verification_uri + user_code. The model shows them to you.
2

Approve in browser, then poll

pollDeviceToken { device_code } repeats every interval seconds until success. The Bearer token is stored automatically and used for subsequent Customer API calls.
3

Logout

revokeToken clears the Bearer token.

Auth (wallet)

1

Load a keypair

generateKeypair (creates fresh) or loadKeypair (from base58 / Solana CLI file).
2

Request a challenge

requestWalletChallenge { wallet_address }.
3

Sign and verify

signMessage { message: <challenge> } then verifyWalletSignature (existing account) or registerWithWallet (new account).

Wallet send

1

Load a keypair

generateKeypair or loadKeypair.
2

Build the transfer

buildSolTransfer { recipient, amountSol } returns a base64 unsigned tx.
3

Sign and broadcast

signAndSendTransaction { transaction } signs with the session keypair, broadcasts, and returns signature + Solscan link.

Top-up

1

Prepare the top-up

prepareTopUp { amount, wallet_address } returns a base64 unsigned USDC transfer + memo.
2

Sign it

Sign with the loaded wallet via signAndSendTransaction, or sign externally.
3

Confirm

confirmTopUp { transaction: <signed-base64> }. OrbitFlare verifies on-chain and credits your balance.

Resources

The server exposes OrbitFlare’s documentation as MCP resources, so the model can pull current docs on demand:

System prompts

Pre-built system / developer prompts ship in the system-prompts/orbitflare/ directory:
  • claude.system.md: concise system prompt for Claude
  • openai.developer.md: concise developer message for OpenAI models
  • full.md: long-form operator playbook (auth flows, top-up, hard guardrails)
Drop one into your host config to give the model end-to-end guidance on when to reach for which tool.

Try it

Once installed, the model picks the right tool automatically:
“What is the SOL balance of Gh9ZwEm…?”
“Show me the last 20 transactions for 7xKXt….”
“What’s a competitive priority fee right now for an account that touches Raydium?”
“Build me a Yellowstone gRPC config that streams Jupiter swap transactions from Frankfurt.”
“Quote 1 SOL → USDC with 0.3% slippage.”
“What is OrbitFlare’s validator vote account, and what would 250 SOL earn per year?”

Source