Application Development
Riza
Connect Riza once and hand every teammate a governed MCP endpoint with 19 tools ready to call from Claude, ChatGPT, Cursor, or any MCP client, inside the same permissions they already have, with every call checked and logged.
Automations & dashboards
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 ship on the Black plan.
Automations
Put Riza work on a schedule.
A trigger starts a sequence of steps: call a Riza tool, transform the result, branch, wait, and ask a person when it matters.
Riza digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch runtimes
Riza
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Riza
Queued
Collections and dashboards
Report on Riza without asking.
Collections hold your own data, written by an automation and read by a dashboard that refreshes on a schedule.
Riza health
Refreshed 4 minutes ago · every 15 minutes · from the runtimes collection
Runtimes
1,284 ↓ 12%
Tools
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Runtimes created
Last 14 days
By workspace
Share of activity
Engineering 34%
Product 27%
Support 21%
Sales 18%
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.
create_a_riza_command
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 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
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 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 a riza runtime by id. Returns: id, deleted. Required: id.
list_all_riza_runtimes
List all runtimes in your riza project. Returns: id, name, language, engine, revision_id, status for each runtime. Max 100 per page.
get_single_riza_runtime_by_id
Retrieve a single riza runtime by id. Returns: id, name, language, engine, revision_id, status. Required: id.
create_a_riza_runtime_revision
Create a new revision for a Riza runtime. Returns: id, runtime_id, status, manifest_file, and additional_python_imports. Required: runtime_id and manifest_file.
list_all_riza_runtime_revisions
List all revisions for a Riza runtime. Returns: id, runtime_id, status, manifest_file, and additional_python_imports for each revision. Required: runtime_id.
get_single_riza_runtime_revision_by_id
Retrieve a single Riza runtime revision by id. Returns: id, runtime_id, status, manifest_file, and additional_python_imports. Required: runtime_id and id.
create_a_riza_secret
Create a secret in your Riza project. Returns: id, name. Required: name, value.
list_all_riza_secrets
List all secrets in your Riza project. Returns: id, name per secret.
create_a_riza_tool
Create a new tool in your riza project. Returns: id, name, language, code, description, input_schema, revision_id, and runtime_revision_id. Required: name, language, code.
list_all_riza_tools
List all tools in your riza project. Returns: id, name, language, code, description, input_schema, and revision_id for each tool. Max 100 per page.
update_a_riza_tool_by_id
Update an existing riza tool's name, language, source code, input schema, or runtime revision by id. Returns: id, name, language, code, description, input_schema, revision_id, and runtime_revision_id. Required: id.
get_single_riza_tool_by_id
Retrieve a single riza tool by id. Returns: id, name, language, code, description, input_schema, revision_id, and runtime_revision_id. Required: id.
create_a_riza_code_execution
Execute a code script in Riza by submitting code in a specified programming language. Returns the execution result including exit_code, stdout, stderr, and duration. Required: language, code.
create_a_riza_function_execution
Execute a function in Riza by submitting code that defines an `execute` function accepting a single argument and returning a JSON-serializable value. Returns: output, output_status, and an execution object containing id, exit_code, stdout, stderr, and duration. Required: language, code.
create_a_riza_tool_execution
Execute a Riza tool by its ID, passing an input payload that matches the tool's defined input schema. Returns: output (the JSON-serializable value produced by the tool's execute function). Required: tool_id.
No tools match your search.
How it works
From Riza account to governed MCP endpoint
Connect
Link a Riza account through Elaichi's hosted connect flow. Credentials are vaulted, so nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Riza tools are exposed, rename them, or freeze arguments.
Authorize
Point Claude, ChatGPT, Cursor, or any MCP client at the one Elaichi endpoint and sign in with OAuth, governed by roles, restrictions, and audit logs.
Put your agents to work in the tools you already use
Start a 14-day Gold trial. Connect a product, curate a toolbox, and paste a governed MCP endpoint into Claude, ChatGPT, or Cursor in minutes.