Which integrations are available for this server?

Enables creating and managing crypto payment intents on the Polygon network via OrcaRail, supporting USDC payments and subscription billing.

How do I use OrcaRail MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@OrcaRail MCP Create a $25 USDC payment intent on Polygon and give me the pay link." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

OrcaRail MCP

Official

by OrcaRail

Overview Schema Related Servers Score Discussions

TypeScript

Local

@orcarail/mcp

Official Model Context Protocol (MCP) server for OrcaRail — accept crypto payments from your AI coding agent.

Runs locally over stdio and wraps the @orcarail/node SDK, so Claude Code, Cursor, Codex, and any other MCP client can create payment intents, manage subscriptions, maintain your product catalog, and look up exchange rates — the same delivery model as Stripe's @stripe/mcp.

Docs: docs.orcarail.com/docs/integration/mcp
Dashboard: app.orcarail.com
npm: @orcarail/mcp

What you can ask your agent

"Create a $25 USDC payment intent on Polygon with return URL https://myapp.com/success and give me the pay link."
"List my active subscriptions and cancel the one for customer@example.com at period end."
"Create a product called Pro Plan with a $29/month recurring price."
"How much is 500 EUR in USDC right now?"

Related MCP server: Safefy MCP

Requirements

Node.js 18+
OrcaRail API key (ak_…) and secret (sk_…) from the dashboard

Quick start

npx -y @orcarail/mcp --tools=all --api-key=ak_live_xxx --api-secret=sk_live_xxx

Or with environment variables (preferred — keeps secrets out of shell history):

export ORCARAIL_API_KEY=ak_live_xxx
export ORCARAIL_API_SECRET=sk_live_xxx
npx -y @orcarail/mcp --tools=all

The server speaks MCP over stdin/stdout; it is meant to be launched by an MCP client, not used interactively. npx -y @orcarail/mcp --help prints usage.

Configuration

Every option is a CLI flag or an environment variable. Flags win.

Flag	Environment variable	Required	Description
`--api-key`	`ORCARAIL_API_KEY`	Yes	API key (`ak_…`)
`--api-secret`	`ORCARAIL_API_SECRET`	Yes	API secret (`sk_…`)
`--api-base`	`ORCARAIL_API_BASE`	No	API base URL. Default `https://api.orcarail.com/api/v1`
`--organization-id`	`ORCARAIL_ORGANIZATION_ID`	No	Default organization for `products.` / `prices.` tools
`--tools`	—	No	`all` (default) or comma-separated tool names

Restrict what the agent can do:

npx -y @orcarail/mcp \
  --tools=payment_intents.create,payment_intents.retrieve,subscriptions.list \
  --api-key=... --api-secret=...

Self-hosted or local API:

npx -y @orcarail/mcp --tools=all --api-base=http://127.0.0.1:3000/api/v1 --api-key=... --api-secret=...

Client setup

Claude Code

claude mcp add orcarail -- npx -y @orcarail/mcp --tools=all --api-key=ak_live_xxx --api-secret=sk_live_xxx

Or pass secrets via env:

claude mcp add orcarail \
  -e ORCARAIL_API_KEY=ak_live_xxx \
  -e ORCARAIL_API_SECRET=sk_live_xxx \
  -- npx -y @orcarail/mcp --tools=all

Verify with claude mcp list.

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "orcarail": {
      "command": "npx",
      "args": ["-y", "@orcarail/mcp", "--tools=all"],
      "env": {
        "ORCARAIL_API_KEY": "ak_live_xxx",
        "ORCARAIL_API_SECRET": "sk_live_xxx"
      }
    }
  }
}

Codex

Add to ~/.codex/config.toml:

[mcp_servers.orcarail]
command = "npx"
args = ["-y", "@orcarail/mcp", "--tools=all"]

[mcp_servers.orcarail.env]
ORCARAIL_API_KEY = "ak_live_xxx"
ORCARAIL_API_SECRET = "sk_live_xxx"

Other MCP clients

Any stdio-capable MCP client works with the same shape: command npx, args ["-y", "@orcarail/mcp", "--tools=all"], credentials in env. For Claude Desktop, use the Cursor JSON block in claude_desktop_config.json.

Tool reference

Tool names follow resource.action. Responses are raw OrcaRail API objects as JSON.

Payment intents

Tool	Arguments	Description
`payment_intents.create`	`return_url` (required); either `price_id` or `amount` + `currency` + `tokenId` + `networkId`; optional `cancel_url`, `description`, `metadata`, `expires_at`, `payment_method_types`, `withdrawal_addresses`	Create a payment intent (returns `client_secret` and payment link)
`payment_intents.retrieve`	`id`	Fetch current status
`payment_intents.update`	`id` + any updatable field	Update before confirmation
`payment_intents.confirm`	`id`, `client_secret`, `return_url`	Confirm and get the hosted pay redirect URL
`payment_intents.complete`	`id`	Mark processing after the customer hits your success URL
`payment_intents.cancel`	`id`	Cancel the intent

tokenId / networkId are UUIDs — see Networks and Tokens.

Subscriptions

Tool	Arguments	Description
`subscriptions.create`	`description` (required); either `price_id` or `interval` + `amount` + `currency` + `token_id` + `network_id`; optional `collection_method`, `total_cycles`, `trial_period_days`, `trial_end`, `payer_email`, `payer_user_id`, `billing_cycle_anchor`, `cancel_at`, `cancel_at_period_end`, `days_until_due`, `interval_count`, `metadata`, `withdrawal_addresses`, `return_url`, `cancel_url`	Create a recurring subscription
`subscriptions.retrieve`	`id`	Fetch a subscription
`subscriptions.update`	`id` + any updatable field, including `pause_collection`	Update
`subscriptions.cancel`	`id`, optional `cancellation_details` (`comment`, `feedback`)	Cancel
`subscriptions.resume`	`id`	Resume a paused subscription
`subscriptions.list`	Optional `status`, `collection_method`, `created` / `current_period_start` / `current_period_end` range filters, `limit`, `starting_after`, `ending_before`	List with cursor pagination
`subscriptions.list_payment_links`	`id`, optional `limit`, `starting_after`, `ending_before`	Cycle invoices for a subscription

Catalog — products and prices

Catalog tools operate on an organization: pass organization_id per call or set a default via --organization-id / ORCARAIL_ORGANIZATION_ID.

Tool	Arguments	Description
`products.list`	optional `organization_id`	List products
`products.create`	`name` (required); optional `description`, `active`, `metadata`, `default_price`, `marketing_features`, …	Create a product
`products.update`	`product_id` + updatable fields	Update a product
`products.delete`	`product_id`	Delete a product
`prices.list`	optional `active`, `recurring`, `limit`	List prices
`prices.create`	`unit_amount_decimal`, `currency`, `token_id`, `network_id` (required); `product` or inline `product_data`; optional `recurring` (`interval`, `interval_count`, `trial_period_days`), `nickname`, `lookup_key`, `active`, `metadata`	Create a one-time or recurring price
`prices.update`	`price_id` + updatable fields	Update a price
`prices.deactivate`	`price_id`	Deactivate a price

Rates and pay

Tool	Arguments	Description
`rates.get_fiat_quote`	`amount`, `currency`	Fiat → USD/USDC quote
`rates.list_currencies`	optional `active`	Supported fiat currencies
`pay.get_by_slug`	`slug`	Payment details by hosted pay slug
`pay.cancel_by_slug`	`slug`	Cancel by pay slug

Error handling

API failures surface to the agent as tool errors with the HTTP status, error type, and message intact, e.g. API error (401): [authentication_error]: …. Nothing is retried automatically.

Programmatic usage

The package also exports its building blocks if you want to embed the server:

import { createServer, startStdioServer, listToolNames } from '@orcarail/mcp';

const { server, tools } = createServer({
  apiKey: process.env.ORCARAIL_API_KEY!,
  apiSecret: process.env.ORCARAIL_API_SECRET!,
  tools: 'all', // or new Set(['payment_intents.create'])
});

console.log(listToolNames()); // all 25 tool names
await startStdioServer(server);

Security

API keys grant full access to the linked organization — treat MCP config files like .env files.
Prefer environment variables over inline --api-key=… args.
Never commit live keys; keep project-level .cursor/mcp.json with secrets out of git.
Scope with --tools to only the operations your agent needs.
Use test keys during development; rotate leaked keys in the dashboard.

Troubleshooting

Symptom	Fix
`Missing credentials` on startup	Pass `--api-key`/`--api-secret` or set `ORCARAIL_API_KEY`/`ORCARAIL_API_SECRET`
`Authentication error` on every call	Verify the key/secret pair; don't mix test and live credentials
`organization_id is required`	Pass `organization_id` in the call or launch with `--organization-id`
Tool missing from the client	Check the `--tools` filter — names must match exactly
Client can't start the server	Ensure Node.js 18+ on the client's PATH; try `npx -y @orcarail/mcp --help`

Development

npm install
npm run build       # tsup → dist/
npm test            # vitest
npm run typecheck   # tsc --noEmit
npm run lint        # eslint

Test against a local MCP inspector:

npx @modelcontextprotocol/inspector node dist/cli.cjs --tools=all --api-key=ak_test_xxx --api-secret=sk_test_xxx

License

MIT

Install Server

license - permissive license

quality

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

1Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Tools

View all tools

Related MCP Servers

satsrail-mcpofficial
Payments & Billing Cryptocurrency Blockchain
SatsRail
A
license
-
quality
C
maintenance
An MCP server that enables AI agents to accept Bitcoin Lightning payments. It allows agents to create orders, generate invoices, check payment status, and manage the full SatsRail merchant API through natural language.
Last updated 2026-07-07
MIT
Safefy MCPofficial
Payments & Billing Finance
Safefy-Pay
A
license
-
quality
D
maintenance
Official MCP server for Safefy, enabling AI agents to manage PIX payments, withdrawals, customers, and transactions via the Safefy payment API.
Last updated 2026-03-05
1
MIT
zuckpay-mcpofficial
Payments & Billing Finance
ZuckPay
A
license
A
quality
A
maintenance
Official MCP server for ZuckPay – create PIX, SPEI, and PayPal charges, and query transactions from your AI assistant.
Last updated 2026-07-21
20
187
MIT
nanocart-mcp
E-commerce & Retail CRM
ByteBunny-io
A
license
-
quality
C
maintenance
Official MCP server for NanoCart, enabling AI agents to manage products, orders, coupons, categories, subscribers, settings, and pull sales reports from your store.
Last updated 2026-07-21
MIT

View all related MCP servers

Related MCP Connectors

Lovable
Official MCP server for Lovable, the AI-powered full-stack app builder.
Qase Test Management
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
gainium-mcp
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants

View all MCP Connectors

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OrcaRail/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server