Riza MCP Server
# Riza MCP Server
[Riza](https://riza.io) offers an isolated code interpreter for your LLM-generated code.
Our MCP server implementation wraps the Riza API and presents
endpoints as individual tools.
Configure with Claude Desktop as below, or adapt as necessary for your MCP client. Get a free Riza API key in your [Riza Dashboard](https://dashboard.riza.io).
```json
{
"mcpServers": {
"riza-server": {
"command": "npx",
"args": [
"@riza-io/riza-mcp"
],
"env": {
"RIZA_API_KEY": "your-api-key"
}
}
}
}
```
The Riza MCP server provides several tools to your LLM:
- `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.
TDQS
Scored across 6 tools
Each tool has a distinct role: create, fetch, edit, list, and execute self-written tools, plus execute_code for arbitrary ad-hoc code. The only potentially overlapping pair, execute_code and execute_tool, is clearly separated by whether the code is a saved tool or not.
All tool names follow a consistent snake_case verb_noun pattern, such as create_tool, fetch_tool, edit_tool, and execute_tool. The minor pluralization in list_tools is predictable and does not break the naming convention.
Six tools is well-suited to the server's purpose of managing and executing self-written tools. Each tool contributes a necessary operation without unnecessary bloat.
The set covers create, read, update, list, and execute, but lacks a delete/remove operation, which is a notable lifecycle gap. Additionally, list_tools references a use_tool that does not exist in the exposed tool set, though execute_tool appears to fill that role.