Arbitrary code execution and tool-use platform for LLMs by Riza
If you want an AI assistant working directly with Riza, the riza mcp server is the bridge. Arbitrary code execution and tool-use platform for LLMs by Riza.
Riza offers an isolated code interpreter for your LLM-generated code.
Once connected, the assistant can call these 6 tools directly:
create_tool — Your LLM can write code and save it as a tool using the Riza Tools API. It can then execute these toolsfetch_tool — Your LLM can fetch saved Riza tools, including source code, which can be useful for editing toolsexecute_tool — Executes a saved tool securely on Riza's code interpreter APIedit_tool — Edits an existing saved toollist_tools — Lists available saved toolsexecute_code — Executes arbitrary code safely on Riza's code interpreter API, without saving it as a toolSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Before the server will start you need to supply one environment variable: RIZA_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Riza sits in that group, and the shape of its toolset — create_tool, fetch_tool, execute_tool among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| create_tool | Your LLM can write code and save it as a tool using the Riza [Tools API](https://docs.riza.io/api-reference/tool/create-tool). It can then execute these tools securely on Riza using execute_tool. |
| fetch_tool | Your LLM can fetch saved Riza tools, including source code, which can be useful for editing tools. |
| execute_tool | Executes a saved tool securely on Riza's code interpreter API. |
| edit_tool | Edits an existing saved tool. |
| list_tools | Lists available saved tools. |
| execute_code | Executes arbitrary code safely on Riza's code interpreter API, without saving it as a tool. |
{
"mcpServers": {
"riza-server": {
"command": "npx",
"args": [
"@riza-io/riza-mcp"
],
"env": {
"RIZA_API_KEY": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| RIZA_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.