ROKI Connect

Connect Remote server

claude mcp add --transport http connect https://mcp.roki.la/mcp

{
  "mcpServers": {
    "connect": {
      "url": "https://mcp.roki.la/mcp"
    }
  }
}

{
  "servers": {
    "connect": {
      "type": "http",
      "url": "https://mcp.roki.la/mcp"
    }
  }
}

Settings > Connectors > Add custom connector
URL: https://mcp.roki.la/mcp

Tools 19 found in our last check

• roki_search_docs

  Search 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 another payment gateway's conventions.

• roki_get_doc_section

  Return 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

  List 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

  Full detail for one operation: method, path, headers, request schema field table, responses, and worked examples.

• roki_get_schema

  Return 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

  Explain 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

  Validate 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 payment rather than an error. The response names what it dropped…

• roki_check_result

  Compare 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 right and the VALUE was wrong. The API answers 201, `warni…

• roki_get_integration_example

  Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.

• roki_get_quickstart

  The minimum viable integration sequence, end to end, including the manual portal steps a developer cannot skip.

• roki_get_authentication_guide

  How authentication works, how the two environments are selected, where credentials come from, and how to store and rotate them safely.

• roki_get_webhook_guide

  Everything 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

  Decide 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 behind them are read from the corpus, so this answer canno…

• roki_verify_webhook_signature

  Check 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 you made. Use it whenever webhook verification rejects rea…

• roki_scaffold_integration

  Return 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 one from memory.

• roki_audit_integration

  Return 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_try

  Runs 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_validate_request says a payload is valid. You never supply a ke…

• roki_sandbox_info

  Whether the sandbox playground is enabled here, which operations it accepts, its limits, and the sandbox test cards.

• roki_status

  Server version, corpus contents and freshness. Safe first call to confirm the connection works. Exposes no credentials and no merchant data.

Details

More developer tools servers See all

• AGILEX Docs

  Official AGILEX robotics product docs: manuals, CAN protocol, firmware, FAQ. Read-only.

• Echoo public catalog

  Read-only Echoo product facts, pricing, documentation and published writing skills.

• 99tests

  Order human-run real-device app tests from your coding agent; verified bugs return as fix prompts.

• LimitReceipts by aiw3b

  Find the AI coding/app-builder plan that fits your usage: limits, prices and plan-fit picks.

• Candor UI docs

  Candor UI docs and component suggestions. Read-only, no key, never serves paid source.

• MoneyTools Tools

  Call for a cheap read-only utility: 100+ tools; free daily tier; not charged on failure