Your payments.Your AI assistant.Your approval.

Connect your AurasPay merchant account to an MCP-compatible AI application. Read payment activity and prepare payment links, with permissions you control.

Set up connection Explore examples

Merchant developer preview · Supported functions, not the entire dashboard.

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.

Connect in three steps.

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

Add the server
In your AI application, add a custom remote MCP server using the URL below.
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.
Ask, review, then continue
Start with a read request. Payment-link creation opens a separate AurasPay review before it runs.

Choose your AI application.

Each person connects their own AurasPay merchant account. AurasPay opens the sign-in and consent screen; the AI application never receives the merchant password.

CodexCLI, desktop and IDE

Add AurasPay once from a terminal. Codex clients on the same host share the MCP configuration.

codex mcp add auraspay --url https://mcp.auraspay.com/api/mcp
codex mcp login auraspay

Restart the desktop app or IDE extension after adding the server. In Codex, use /mcp to confirm that AurasPay is connected.

Claude CodeRemote HTTP + OAuth

Add AurasPay for the current user, then open the MCP menu in Claude Code to complete OAuth in your browser.

claude mcp add --transport http --scope user auraspay https://mcp.auraspay.com/api/mcp
# Then run /mcp inside Claude Code

Choose AurasPay from /mcp and authenticate. Approve only the permissions you want this client to use.

Other MCP clientsCompatible remote clients

Choose Streamable HTTP, paste the server URL, and select OAuth when the client asks for authentication.

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

The client must support remote Streamable HTTP MCP and OAuth with PKCE/Dynamic Client Registration. Client behavior varies; use its own MCP setup screen or documentation.

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 OAuth 2.0 with PKCE. Discover permissions, request only what you need, and handle uncertain writes without automatic retries.

Read technical guide

Does it work with every AI application?

The application must support the required MCP transport and OAuth flow. Model choice is independent; named-client certification and marketplace listings are not claimed.

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?

Not yet. This is a merchant developer preview. Available tools depend on enabled features and your approved permissions. Read activity, prepare payment links, and consult the technical guide for the current tool catalog. Features marked coming soon remain unavailable.