Code Interpreter Agent by Nova (CIVAI) is an MCP server published by co.civai.nova, hosted at nova.civai.co. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 8 tools, including interpreter__generate_code_only, interpreter__generate_and_execute_code, interpreter__debug_update_existing_code, interpreter__converse, command__bash.
I do everything related to coding and execution tasks
153 connections through 4 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Code interpreter (runner operator): generate code only
| Parameter | Type | Description |
|---|---|---|
| detail | string | Specific parameters for this action. |
{
"name": "interpreter__generate_code_only",
"description": "Code interpreter (runner operator): generate code only",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string",
"description": "Specific parameters for this action."
}
}
}
}Code interpreter (runner operator): generate and execute code
| Parameter | Type | Description |
|---|---|---|
| detail | string | Specific parameters for this action. |
{
"name": "interpreter__generate_and_execute_code",
"description": "Code interpreter (runner operator): generate and execute code",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string",
"description": "Specific parameters for this action."
}
}
}
}Code interpreter (runner operator): debug update existing code
| Parameter | Type | Description |
|---|---|---|
| detail | string | Specific parameters for this action. |
{
"name": "interpreter__debug_update_existing_code",
"description": "Code interpreter (runner operator): debug update existing code",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string",
"description": "Specific parameters for this action."
}
}
}
}Reply conversationally when the request is ambiguous or needs clarification.
| Parameter | Type | Description |
|---|---|---|
| reply_hint | string | Optional hint for the conversational reply. |
{
"name": "interpreter__converse",
"description": "Reply conversationally when the request is ambiguous or needs clarification.",
"inputSchema": {
"type": "object",
"properties": {
"reply_hint": {
"type": "string",
"description": "Optional hint for the conversational reply."
}
}
}
}Terminal command (runner operator): bash
| Parameter | Type | Description |
|---|---|---|
| detail | string | Specific parameters for this action. |
{
"name": "command__bash",
"description": "Terminal command (runner operator): bash",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string",
"description": "Specific parameters for this action."
}
}
}
}Terminal command (runner operator): sh
| Parameter | Type | Description |
|---|---|---|
| detail | string | Specific parameters for this action. |
{
"name": "command__sh",
"description": "Terminal command (runner operator): sh",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string",
"description": "Specific parameters for this action."
}
}
}
}Terminal command (runner operator): zsh
| Parameter | Type | Description |
|---|---|---|
| detail | string | Specific parameters for this action. |
{
"name": "command__zsh",
"description": "Terminal command (runner operator): zsh",
"inputSchema": {
"type": "object",
"properties": {
"detail": {
"type": "string",
"description": "Specific parameters for this action."
}
}
}
}Reply conversationally when the request is ambiguous or needs clarification.
| Parameter | Type | Description |
|---|---|---|
| reply_hint | string | Optional hint for the conversational reply. |
{
"name": "command__converse",
"description": "Reply conversationally when the request is ambiguous or needs clarification.",
"inputSchema": {
"type": "object",
"properties": {
"reply_hint": {
"type": "string",
"description": "Optional hint for the conversational reply."
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.