MCP & AI tools

Connect an AI client to Atlas Pay’s public developer documentation. Search the guides, read the full Markdown, and retrieve the OpenAPI contract without sharing a merchant API key.

This is a read-only documentation server, not a payment agent. It cannot access your workspace, customers, transactions, credentials, or account balance. It cannot create checkouts or issue refunds.

Connect your client

Use a client that supports remote MCP over Streamable HTTP. Add a custom server and paste the endpoint for the deployment you want to use:

https://dashboard.atlaspay.sh/mcp

This endpoint becomes available after the updated frontend is deployed. For the local preview, use http://localhost:3034/mcp from a client running on the same computer. A hosted AI service cannot reach your computer’s localhost.

The Copy MCP URL button uses the origin of the page you are viewing, so a local preview copies the local endpoint. No API key or authorization header is needed. Never paste merchant keys or payment details into a documentation query.

Some clients accept a configuration shaped like this; others use a server-connection screen. Follow your client’s remote HTTP configuration format. This is not a local stdio command.

{
  "mcpServers": {
    "atlas-pay-docs": {
      "url": "https://dashboard.atlaspay.sh/mcp"
    }
  }
}

Available tools

Tool	Input	Result
`search_docs`	`query` (1–200 characters); optional `limit` (1–8)	Matching public guides with document IDs, source URLs, and short excerpts
`get_doc`	`id` from the list below	The full guide as Markdown, identical to its copy/download export
`get_openapi`	No arguments	The public OpenAPI 3.1 contract for the merchant API

Document IDs: index, api, products, webhooks, wordpress, wix, testing, mcp, and integrations.

Search uses local keyword matching, not an AI model or an external search service. For exact request fields and response schemas, retrieve the OpenAPI contract instead of relying on a search excerpt.

Resources

Clients that support MCP resources can read each guide at atlas-pay://docs/{id} and the API contract at atlas-pay://openapi. Resource reads and tool reads use the same public source files as this website.

Try asking your client:

Find the WordPress installation guide and explain where the server-side secrets belong.
Read the webhook guide and outline signature verification and safe retries.
Get the OpenAPI contract and explain how to verify payment before fulfilling an order.
Read the testing guide and turn the launch gates into an acceptance checklist.

Review generated integration code before use. Documentation access does not certify an implementation or remove the test-mode and live-launch requirements.

Markdown without MCP

Every documentation page and the integrations page has Copy as Markdown, Download .md, and View raw controls. Code blocks, tables, links, and warnings are included; navigation and interface controls are not.

For example, read the testing guide as Markdown. Exports use the canonical public website for source links, even when you copy them from a local preview. They describe the same build’s documentation, which may be newer than the currently deployed site.

Transport & boundaries

The endpoint runs in the existing frontend’s Node.js runtime. Requests are stateless; there is no database, persistent session, background agent, or connection to the payment backend. It supports Streamable HTTP clients using the current MCP revision and legacy stateless negotiation.

Requests are limited to 32 KiB. Only registered public document IDs and the public OpenAPI file are readable. Arbitrary file paths, remote URL fetching, and merchant actions are not supported. The endpoint validates hosts and browser origins; cross-origin browser access is not enabled. Native/server-side MCP clients do not need a browser origin header.

Opening /mcp as a normal browser page returns HTTP 405 by design. Use an MCP client to connect; read this guide in the browser. Monitor the normal docs page for website uptime, and use a protocol-aware check for MCP health.

Before public launch, verify the deployed endpoint from your intended client, keep the SDK patched, and configure platform-level abuse/rate-limit controls. This developer preview does not claim production load or soak certification. A future merchant-action MCP would require separate authentication, scoped permissions, audit records, idempotency, and explicit confirmation for money-moving actions.

See the official MCP HTTP server guide and MCP specification for protocol details.