← roki.la

INDIVIDUAL MCP TOOL

roki_get_quickstart

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

roki.lanone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.roki.la/mcp

No auth detected

Connect to this endpoint to inspect the live schema for roki_get_quickstart and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

roki.la

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.roki-connect]
url = "https://mcp.roki.la/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "roki-connect": {
      "type": "http",
      "url": "https://mcp.roki.la/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: roki-connect
Remote MCP URL: https://mcp.roki.la/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "roki-connect": {
      "url": "https://mcp.roki.la/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "roki-connect": {
      "type": "http",
      "url": "https://mcp.roki.la/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "roki-connect",
  "transport": "streamable-http",
  "url": "https://mcp.roki.la/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • roki_search_docs — Search the official ROKI Connect corpus (integration guide, API operations and schemas) and return ranked excerpts.
  • roki_get_doc_section — Return the complete text of one section of the integration guide, by number (e.
  • roki_list_operations — List every operation the API actually exposes, plus the operations that are documented as NOT existing.
  • 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.
  • 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.
  • roki_validate_request — Validate a payload against the official schema WITHOUT sending it, and check the business rules the API enforces.
  • 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.