Polygon OMS MCP server
21 operations0 webhooks
Polygon Open Money Stack (OMS) payments API for moving money between crypto and fiat, with quotes, transfers, wallets, customers and webhooks.
Try Polygon OMS with your agent
Connect Polygon OMS, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Polygon OMS on my account, then run one read-only example and show me the result.
Polygon OMS tools and triggers
Tools are what your agent can do in Polygon OMS through Corsair's MCP server. Triggers are the Polygon OMS events a routine can start from.
Customers
- CreateWrite
Create a customer. Individuals need a first and last name; businesses need a legal name and email. Identity verification follows the project policy
customers.create
- DeleteDestructive
Delete a customer. OMS returns the record in its offboarded state
customers.delete
- GetRead-only
Read one customer with its onboarding status
customers.get
- ListRead-only
List customers, filtered by status, email, external id or creation window, with cursor paging
customers.list
- UpdateWrite
Update a customer's details, or request additional endorsements. Personal data fields are write-only
customers.update
Webhooks
- CreateWrite
Register a webhook endpoint. The HMAC signing key is returned only here, so store it when the call returns
webhooks.create
- DeleteDestructive
Delete a webhook endpoint. Deliveries stop immediately and the signing key is discarded
webhooks.delete
- GetRead-only
Read one webhook endpoint
webhooks.get
- ListRead-only
List webhook endpoints with their delivery counts and cursor paging
webhooks.list
- UpdateWrite
Change a webhook's URL, subscriptions or delivery settings
webhooks.update
Wallets
- BalanceRead-only
Read one wallet balance in its asset, with an estimated value. The balance can be negative after a clawback
wallets.balance
- CreateDestructive
Create a custodial, noncustodial or fiat wallet for a customer. OMS has no route to delete a wallet, so a live wallet stays on the customer
wallets.create
- GetRead-only
Read one wallet by id
wallets.get
- ListRead-only
List wallets, scoped to a customer or type, with balance ordering and cursor paging
wallets.list
Transactions
- CreateDestructive
Accept a quote and move the money. This is the irreversible step: pricing is locked at the quote and the transfer starts as soon as OMS accepts it
transactions.create
- GetRead-only
Read one transaction with its status, pricing and transfers
transactions.get
- ListRead-only
List transactions filtered by status, customer, wallet, precursor or creation window, with cursor paging
transactions.list
Quotes
- CreateWrite
Price a transfer: set the amount on one side and OMS calculates the other. Nothing moves until a transaction accepts the quote
quotes.create
- GetRead-only
Read one quote with its status and pricing
quotes.get
Cash Locations
- ListRead-only
List the retail cash locations in range, nearest first, with cursor paging
cashLocations.list
Networks
- ListRead-only
List the networks, rails and assets this project can route, with cursor paging
networks.list
Connect Polygon OMS to Claude, ChatGPT or Cursor
- 1
Connect Polygon OMS in Corsair
Add your Polygon OMS API key once in Corsair. Corsair stores the credential encrypted and makes the Polygon OMS API calls for your agent, so it never goes into a prompt or a config file. Connect Polygon OMS
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Polygon OMS. On a ChatGPT personal plan, connect Polygon OMS here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Polygon OMS's read and write operations run right away and its 4 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/polygon, add the Polygon OMS plugin, and connect with an API key. Then call methods like corsair.polygon.api.cashLocations.list() from your app. Corsair keeps each tenant isolated.
Yes. Polygon OMS requires an API key from your Polygon OMS account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Polygon OMS, GitHub, Notion, Stripe, and the rest. Trigger Polygon OMS from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for polygon Open Money Stack (OMS) payments API for moving money between crypto and fiat, with quotes, transfers, wallets, customers and webhooks. Common builds include sync jobs, admin tooling, and agents that call Polygon OMS APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Polygon OMS API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/polygon in the open repo. When Polygon OMS ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Polygon OMS data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Polygon OMS data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Polygon OMS on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 4 destructive Polygon OMS operations. You can change a link's mode at hub.corsair.dev/me.