Agents Index

ROKI Connect

Online

Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.

Visit publisherConnectJSON

What it can do: 19 tools

  • roki_search_docs read-onlySearch the official ROKI Connect corpus (integration guide, API operations and schemas) and return ranked excerpts. Use this first when you need any ROKI-specific fact. Never answer a ROKI question from memory or from an
  • roki_get_doc_section read-onlyReturn the complete text of one section of the integration guide, by number (e.g. "14"), sub-number ("12.1") or title fragment ("webhook").
  • roki_list_operations read-onlyList every operation the API actually exposes, plus the operations that are documented as NOT existing. Call this before writing any integration code so you never invent an endpoint.
  • roki_get_operation read-onlyFull detail for one operation: method, path, headers, request schema field table, responses, and worked examples.
  • roki_get_schema read-onlyReturn a fully dereferenced JSON Schema by name (e.g. "PaymentCreateRequest", "Payment", "WebhookEvent"). Use it to know the exact field names, types and constraints.
  • roki_get_error read-onlyExplain an HTTP status or an error message returned by the ROKI API: what it means, the likely cause and what to do. Use this instead of guessing when an integration fails.
  • roki_validate_request read-onlyValidate a payload against the official schema WITHOUT sending it, and check the business rules the API enforces. Critical for this API: it ignores unknown fields and returns 201, so a typo produces a misconfigured payme
  • roki_check_result read-onlyCompare the payment the API returned against the body you sent, and report anything that does not match. Every other check here looks at what you SEND. This one exists for the errors that survive that: the field name was
  • roki_get_integration_example read-onlyReturn a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.
  • roki_get_quickstart read-onlyThe minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.
  • roki_get_authentication_guide read-onlyHow authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.
  • roki_get_webhook_guide read-onlyEverything about webhooks: portal registration, event types, payload shape, HMAC signature verification over the raw body, idempotent processing, and the polling fallback.
  • roki_choose_integration_mode read-onlyDecide how to integrate ROKI Connect for a given project (web checkout, embedded card fields, mobile app, invoices or recurring billing) and get the constraints that apply before writing code. The modes and the endpoints
  • roki_verify_webhook_signature read-onlyCheck a ROKI-Signature header against the raw body and the signing secret. When it fails, this does not just say "invalid" - it tries the specific wrong constructions developers actually write and tells you which mistake
  • roki_scaffold_integration read-onlyReturn the full runnable skeleton for a stack: credential storage, API client, checkout flow, webhook handler with signature verification, and the polling fallback. Use it to start an integration instead of assembling on
  • roki_audit_integration read-onlyReturn the checklist to audit existing ROKI code, ordered by how badly each item fails in production. Use it when reviewing an integration you did not write, or before going live.
  • roki_sandbox_tryRuns a documented operation against the ROKI sandbox using THIS SERVER'S own test credential, and returns the actual response. Use it to prove an integration works instead of assuming it does - especially after roki_vali
  • roki_sandbox_info read-onlyWhether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.
  • roki_status read-onlyServer version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.

Connect it

Claude Code
claude mcp add --transport http roki-connect https://mcp.roki.la/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.roki.la/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "roki-connect": {
      "url": "https://mcp.roki.la/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "roki-connect": {
      "type": "http",
      "url": "https://mcp.roki.la/mcp"
    }
  }
}

Questions

What does ROKI Connect do?

Verified ROKI Connect payments contract for coding agents: operations, schemas, validator. It exposes 19 tools to AI assistants.

What tools does ROKI Connect provide?

19 tools, including roki_search_docs, roki_get_doc_section, roki_list_operations, roki_get_operation, roki_get_schema, roki_get_error, roki_validate_request, roki_check_result, roki_get_integration_example, roki_get_quickstart, roki_get_authentication_guide, roki_get_webhook_guide….

How do I connect ROKI Connect to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.roki.la/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does ROKI Connect require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is ROKI Connect online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes ROKI Connect?

roki.la. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Automation & Integrations