Skip to content

Application Development

Riza MCP connector

The Riza connector lets Claude, ChatGPT, Cursor, or any MCP client run code, call tools, and manage runtimes and secrets in Riza, with each request tied to the person who signed in and recorded in an audit log.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Riza to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Riza once

  1. Open Connections, choose Add connection, and pick Riza.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Riza API key. One person generates a token in Riza and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

riza
Riza
Apache Airflow
Boomi
Browserbase
Caspio
Cloudflare
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Riza to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Riza to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Riza to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Riza to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Riza on Elaichi See pricing

Use cases

What teams do with Riza through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Engineering

    Run a snippet safely before shipping it

    Ask the agent to execute a piece of code in a Riza runtime and report what came back. Check the result without touching a laptop or a production box.

  • Platform

    Set up a new runtime with its packages

    Describe the language and dependencies you need, and the agent creates the Riza runtime and a revision to match. List what already exists first so nothing is duplicated.

  • Data

    Turn a one-off script into a reusable tool

    Give the agent a working function and have it saved as a Riza tool, then run it again with new inputs whenever the question comes up. Update the tool as the logic changes.

  • Security

    Keep credentials out of the code itself

    Store an API token as a Riza secret so scripts can reference it by name. Review the list of secrets in place before a new runtime goes live.

  • Support

    Reproduce a customer problem in isolation

    Run the exact code a customer sent inside a Riza runtime and see the error for yourself. Pull up the execution afterward to share the output with the engineer who owns the fix.

  • Operations

    Review what ran and clean up old runtimes

    List recent Riza executions and check a single one by ID when something looks off. Remove runtimes nobody uses any more so the account stays tidy.

Try asking

  • “Which Riza commands failed in the last 24 hours?”
  • “List every Riza runtime revision created this week.”
  • “Summarize Riza execution volume by runtime for the sprint.”

See all 19 Riza tools below

AI tools

Riza tools for your AI agents

19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Riza, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Riza gets you

6 screens from the product, each doing one job for your Riza account.

The agent

Ask about Riza executions in plain language.

Starter prompts read live commands, runtimes and executions and answer in seconds.

  • commands
  • runtimes
  • executions
  • secrets

Ask Elaichi to work across your apps.

Which Riza commands failed in the last 24 hours?

List every Riza runtime revision created this week.

Summarize Riza execution volume by runtime for the sprint.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Riza.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

 • Connected 4 minutes ago
Cursor
S

Sofia Ricci

 • Connected 2 hours ago
ChatGPT
C

Clara Nowak

 • Connected Yesterday

Tool catalog

19 Riza tools ready without custom code.

Commands, runtimes, revisions, secrets and executions are covered by name and method.

  • Create a Riza command
  • List all Riza executions
  • Get single Riza execution by ID
  • Create a Riza runtime
ElaichiTools
Tool Action Description
Create a Riza command Create Execute a script in riza's secure, isolated sandbox environment. Returns: id, exit_code, stdout, stderr, and duration (in milliseconds). Required: language, code.
List all Riza executions List List executions in your Riza project. Returns: id, language, exit_code, duration, started_at, and details (per-execution request/response detail object). Optionally filter to only failed executions using only_non_zero_exit_codes.
Get single Riza execution by ID Get Retrieve a single Riza execution by id. Returns: id, language, exit_code, duration, started_at, and details (per-execution request/response detail object). Required: id.
Create a Riza runtime Create Create a new runtime in riza with a specified language and manifest file. Returns: id, name, language, engine, revision_id, status. Required: name, language, manifest_file.
Delete a Riza runtime by ID Delete Delete a riza runtime by id. Returns: id, deleted. Required: id.

Toolboxes

Every team gets its own Riza toolbox.

Curate one toolbox per team, each scoped to the Riza work it does.

  • Platform
  • Backend
  • Security
  • Data
ElaichiToolboxes
Name Source template Tools Created

Platform toolbox

Riza · runtimes and revisions

 Riza starter 18 Mar 4, 2026

Backend toolbox

Riza · commands and executions

 — 9 Mar 2, 2026

Security toolbox

Riza · secrets and access

 — 24 Feb 27, 2026

Data toolbox

Riza · execution logs and reporting

 Riza starter 6 Feb 19, 2026

AI Tooling toolbox

Riza · tools and command drafts

 — 31 Jan 30, 2026

Support toolbox

Riza · failed executions and triage

 — 12 Jan 22, 2026

Shared connections

Teammates run Riza commands without a credential.

One person connects the Riza account, teams and members work through it.

  • Platform
  • Backend EMEA
  • Security
  • Data
ElaichiConnections
Connection Scope Status Access
RI

Riza (Platform)

Connected by Emma Laurent

 Personal • Active 1 team · 6 members
RI

Riza (Backend EMEA)

Connected by James Whitfield

 Organization • Active 3 teams · 24 members
RI

Riza (Security)

Connected by Sofia Ricci

 Organization • Active 2 teams · 11 members
RI

Riza (Data)

Connected by Daniel Ortega

 Personal • Needs re-auth 1 team · 3 members
RI

Riza (AI Tooling)

Connected by Clara Nowak

 Personal • Active Not shared
RI

Riza (Support)

Connected by Michael Brennan

 Personal • Active 2 teams · 9 members

Audit log

Answer who ran which Riza execution.

Append-only rows record time, person, action, type and the Riza resource touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emma Laurent

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

James Whitfield

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
S

Sofia Ricci

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
D

Daniel Ortega

[email protected]

 Riza Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
C

Clara Nowak

[email protected]

 Riza Commands Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
M

Michael Brennan

[email protected]

 Riza Commands List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, Riza work runs through.

Six steps fetch executions, group them, draft a digest, await approval, post back.

Riza digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch commands

    Riza

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    Riza

    Queued

Collections and dashboards

Riza runtime health, computed on a schedule.

Four metrics, 14 days of executions created and a per team breakdown, no model.

Riza health

Refreshed 4 minutes ago · every 15 minutes · from the commands collection

Live

Commands

1,284 ↓ 12%

Runtimes

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Commands created

Last 14 days

By team

Share of activity

Platform 34%

Backend EMEA 27%

Security 21%

Data 18%

Related connectors

More from the catalog

Browse all 400+ connectors →

FAQ

Frequently asked questions

How do I connect Riza to Claude?

Connect Riza in Elaichi first: paste the API key from your Riza account when prompted, and the connection is ready. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in Riza and no client ID or secret to generate.

Does Riza work with ChatGPT and Cursor as well as Claude?

Yes. Once Riza is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Riza once and every client picks it up.

What can an AI agent actually do with my Riza account?

Through Elaichi an agent can run code, call a saved function, or execute a tool in Riza and hand you the output. It can create and list runtimes, add revisions with new packages, save and update tools, store secrets, and look up past executions by ID. It cannot delete tools, secrets, or executions, because Riza does not expose that through this connector.

Does connecting Riza give the AI access to everything in my Riza account?

An agent working through Elaichi can only do what the Riza API key it was connected with allows, and Elaichi can narrow that further with restrictions. It never widens access beyond what the person who connected Riza already has. Every call is recorded against the person who made it.

Can my team share one Riza connection?

Yes. One person connects Riza in Elaichi and shares the connection with a team, and nobody else ever sees or handles the Riza API key. Each teammate still signs in to Elaichi as themselves, so the audit log shows exactly who ran which code or created which runtime.

Can I stop an agent from deleting runtimes or changing tools in Riza?

Yes. Restrictions in Elaichi apply per action, so you can allow running code in Riza while blocking runtime deletion or tool updates. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

What happens to a Riza connection when someone leaves the company?

Offboarding a person in Elaichi ends their access to Riza at once, across every client they used. If they had shared a Riza connection with a team, it keeps working for everyone else. Disconnecting Riza once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Riza in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Riza Talk to us