AurasPayDevelopers

Your payments.Your AI assistant.Your approval.

Connect your AurasPay merchant account to an MCP-compatible AI application. Work with payments, reports, integrations and merchant operations through permissions you control.

Live merchant MCP · Up to 41 scoped tools, depending on enabled features and approved permissions.

Try a request

Prepare a payment link, then let me review it before creation.

The assistant prepares the request. You review the amount, network and receiving address on AurasPay before a link is created. Creating a link does not send funds or confirm payment.

Illustrative request — no action is executed here.

Available today

Find AurasPay MCP where you already work.

Discover AurasPay MCP in leading public directories, connect it to your preferred AI workspace and start with secure permissions you control.

More of your merchant workspace, through scoped tools.

Depending on enabled features and the permissions you approve, AurasPay MCP covers payments and reports, account and profile, integrations and webhooks, support, wallet ownership, preferences and referrals through scoped OAuth. Supported changes stay behind separate human approval in AurasPay.

Published in public MCP directories

Open the confirmed public AurasPay listing in each independent directory. A listing supports discovery; it is separate from the direct MCP connection.

Connect with AurasPay MCP.

Use the production endpoint, follow the setup guide or explore the public repository to connect securely from your preferred MCP-compatible client.

Connect from your preferred AI workspace

Connect directly today from Codex, Claude Code, Gemini CLI, Devin, Cursor, Windsurf, Visual Studio Code, GitHub Copilot CLI or Cline using the production MCP endpoint.

Third-party marks identify supported clients and public directories only; they do not imply endorsement.

AGENTIC CHECKOUT

Available on Base · USDC

Need a buyer agent to pay an existing AurasPay link?

Agent Checkout lets buyer agents resolve an existing payment link, prepare an exact external-wallet transaction, submit its proof and confirm the authoritative payment status through x402 v2.

Explore Agentic Payments

Connect in three steps.

Start from an AI application that supports remote MCP and OAuth.

  1. Add the server

    In your AI application, add a custom remote MCP server using the URL below.

  2. Sign in and choose permissions

    Approve only an application you trust. Your password stays on AurasPay, not in the chat. If sign-in opens separately, return to the authorization page afterwards.

  3. Ask, review, then continue

    Start with a read request. Payment-link creation opens a separate AurasPay review before it runs.

Remote MCP server URL

https://mcp.auraspay.com/api/mcp

Streamable HTTP · OAuth 2.0 + PKCE

Control what your assistant can do.

Read what you allow

Payment requests, reports and account information depend on the scopes you approve.

Review before changes

Payment links and supported changes require a separate review on AurasPay.

Disconnect when needed

Revoke a connection to block future access. This does not undo earlier actions or erase data already shared.

Manage connections

Built for developers.

Use Streamable HTTP and scoped OAuth 2.0 with PKCE. Discover permissions, request only what you need, require human approval for changes, and handle uncertain writes without automatic retries. A payment link is a request—not proof of payment.

Read technical guide
Does it work with every AI application?

The application must support the required MCP transport and OAuth flow. Direct setup guides are available for the clients shown above, and other compatible clients can use the published endpoint.

Can my assistant send funds?

Payment-link creation creates a payment request, not a wallet transfer. It does not prove payment. Never share a seed phrase, private key, password or API secret in an AI conversation.

Is every dashboard function available?

No. The live catalog exposes up to 41 tools, depending on enabled features and your approved permissions. Provider-gated or unavailable dashboard functions are not exposed. Consult the technical guide for the current catalog.