Skip to content

Riza MCP connector

The Riza connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Which Riza commands failed in the last 24 hours?

Working in Riza with Elaichi

  • List all Riza executions
  • Get single Riza execution by ID
  • List all Riza runtimes
Ask anything…
Governance / Audit log Last 24 hours
Riza List all Riza runtimes Emily Carter · ChatGPT · 9:41 AM Done
Riza Get single Riza execution by ID Emily Carter · ChatGPT · 9:41 AM Done
Riza List all Riza executions Emily Carter · ChatGPT · 9:41 AM Done
Riza Create a Riza command Megan Brooks · Claude · 9:38 AM Done
Riza Create a Riza runtime Ryan Hayes · Cursor · 9:35 AM Done

How to connect Riza to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Riza MCP connector for 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.

Riza MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Riza MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.

Riza MCP connector for 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.

Riza MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

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.

What teams do with Riza through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Riza is logged.

  • 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 →

What connecting Riza gets you

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

Elaichi Agent

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, Cursor or Microsoft Copilot

The agent

Ask about Riza executions in plain language.

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

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

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

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Riza.

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

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.

Tool catalog

19 Riza tools ready without custom code.

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

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

Toolboxes

Every team gets its own Riza toolbox.

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

ElaichiConnections
Connection Scope Status Access
RI

Riza (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
RI

Riza (Backend EMEA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
RI

Riza (Security)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
RI

Riza (Data)

Connected by Tyler Reed

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

Riza (AI Tooling)

Connected by Ryan Hayes

Personal • Active Not shared
RI

Riza (Support)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates run Riza commands without a credential.

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

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Riza Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Riza Commands Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Riza Commands List Toolbox

Audit log

Answer who ran which Riza execution.

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

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Riza digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    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 Jake Morgan

    Approve
  6. Post the digest

    Riza

    Queued

Automations

A schedule fires, Riza work runs through.

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

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%

Collections and dashboards

Riza runtime health, computed on a schedule.

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

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Riza

All three can connect Riza to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Riza, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Riza tools Allow or restrict single Riza tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Riza call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

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.

Questions, answered

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, Microsoft Copilot, 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 restricting runtime deletion or tool updates. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

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, Microsoft Copilot, and every other client at the same time.

Does the Riza MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Riza is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Riza?

Yes. Both let Claude, ChatGPT or Cursor use Riza. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Riza call.

How is Elaichi different from Composio for Riza?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Riza: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Riza in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot