MCP

Connect your AI assistant to Renaska

Ask your AI to explore Renaska, create your account and set up your business — all from chat, no forms to fill out.

Endpointhttps://bk.renaska.com/mcp

Paste this URL into your AI client.

What you can do

Explore Renaska

Your AI can look up which modules Renaska offers and how pricing works, to see if it fits your business.

Create your account by chatting

You tell your AI about your business and it signs you up. You verify your email and set your password from the email we send you.

Configure your business

Your AI can adjust your business info and turn on modules, once you've verified your email from the email we send you.

Security

The AI never asks for or sees your password or card details — anything sensitive travels by email as a single-use link.

How to connect

Pick your AI client and follow these steps.

Claude

  1. Settings → Connectors → Add custom connector.
  2. Paste the endpoint URL above.
  3. If you already have an account, Claude takes you to the Renaska login to authorize access.
  4. If you don't have an account yet, ask Claude to help you create one.

ChatGPT

  1. Settings → Connectors → Add.
  2. Paste the endpoint URL. ChatGPT detects the authorization automatically.
  3. Authorize with your Renaska session.

Other agents

  1. Generate an rnk_live_… key from Settings → API & MCP Keys.
  2. Send it as the Authorization: Bearer … header on every call.
  3. Use this for scripts or any agent that doesn't support interactive login.

Your rnk_live_… key is a secret: paste it only into the connector or server config, never into a public chat.

What this MCP doesn't do

This server covers discovery, onboarding and account configuration — it doesn't expose business operations (creating orders, products, customers, etc). For that, use Renaska's public API.

Technical reference for agents and developers

Streamable HTTP transport (stateless) — a single endpoint, JSON-RPC 2.0 over HTTP.

Available tools

17 tools organized into 3 groups by the credential they require.

Group A — Discovery

No credentials

Read-only. Any MCP client can call these without authenticating.

  • pingTrivial liveness check — returns ok:true and the server timestamp.
  • list_modulesLists every Renaska module (slug, name, description, features) in the requested locale.
  • list_capabilitiesStatic overview of Renaska modules and AI channels.
  • get_pricingRenaska pricing: a single flat plan (no per-module pricing) plus AI usage.
  • recommend_for_businessGiven a free-text business description, recommends relevant modules.

Group B — Onboarding

Session onboardingToken

Create and configure a new account. The onboarding session token identifies the tenant — no tool takes a tenantId parameter.

  • start_signupCreates the account with basic data. Password and payment are ALWAYS sent by email with secure links — never asked for or shown in the chat.
  • check_signup_statusChecks onboarding progress (email verified, password set, card on file, tenant provisioned).
  • resend_emailRe-sends the verify-email or set-password email.
  • configure_businessUpdates the business info (name, legal name, tax id, address, timezone, locale, currency). Country cannot be changed.
  • set_modulesActivates and/or deactivates Renaska modules. Base modules cannot be deactivated.
  • get_recommended_setupSuggests relevant modules for THIS tenant from a free-text description. Suggest only — never activates anything.
  • get_setup_statusSummarizes the onboarding state: basic data complete, active modules, card on file, email verified.
  • request_payment_linkSends a secure Stripe-hosted link by email to add a payment method. The link is never returned in the chat.

Group C — Existing account

API key or OAuth token

Configuration for an already-created account. Requires a credential with the mcp:query or mcp:admin scope — the tenant is resolved from the credential, never from a parameter.

  • tenant_configure_businessSame as configure_business, for an existing account. Requires the mcp:admin scope.
  • tenant_set_modulesSame as set_modules, for an existing account. Requires the mcp:admin scope.
  • tenant_get_configReturns the tenant's current settings (business info, active modules) — never tokens, keys or secrets. Requires the mcp:query scope.
  • tenant_recommend_setupSame as get_recommended_setup, for an existing account. Requires the mcp:query scope.

Authentication

API key

Prefixed rnk_live_, with mcp:query (read-only) and mcp:admin (read/write) scopes. A key is never issued with full (*) access to the MCP namespace. Created from Settings → API & MCP Keys.

OAuth 2.1

Mandatory PKCE, dynamic client registration (DCR), a consent screen backed by your Renaska session, and single-use opaque tokens per authorization code. Built for interactive connectors like Claude and ChatGPT.

AI-driven onboarding flow

The AI never asks for or sees a password or a card number — anything sensitive travels by email as a single-use link.

  1. 1

    Discover

    The AI calls list_modules / get_pricing / recommend_for_business to understand what Renaska offers and what fits the business.

  2. 2

    Create the account

    start_signup creates the user with basic data (name, email, business). Renaska sends two emails: one to verify the address, one to set the password.

  3. 3

    The person verifies and sets a password

    From the email, the person confirms their address and sets their password on the Renaska site — never in the chat with the AI.

  4. 4

    Payment

    If applicable, request_payment_link emails a Stripe link to add a payment method. The link is never returned in the tool's response.

  5. 5

    Configure

    With the onboardingToken (or already with an API key/OAuth), the AI adjusts business info and toggles modules with configure_business / set_modules.