Spins up a Python sandbox, uploads files into it, runs code or shell commands, and returns the file that comes out.
5actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro executes Python code in a sandbox and returns the results, stdout, stderr, and any errors. Support agents can run calculations or tests without leaving the conversation, solving problems on the fly.
Ayro runs a terminal command in the sandbox environment and returns the output and exit code. Agents can perform system operations, check file states, or run scripts without leaving the support context.
Ayro creates a new sandbox environment for executing Python code in a Jupyter notebook cell. Each conversation gets an isolated workspace, ensuring customer data stays separate and sessions don't interfere.
Each card is one request a support team gets, and the Codeinterpreter actions Ayro runs to close it.
Ayro creates a sandbox, executes the code in a Jupyter cell and reads back the result, stdout, stderr and any error, dropping to a terminal command when a package install or a file listing is needed first.
Ayro uploads the attachment into /home/user, works on it inside the sandbox, and returns the CSV or chart image the script wrote there, which is how visual output travels when the code runs remotely.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Codeinterpreter actions it has and picks the ones a request needs.
Authorize the Codeinterpreter account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Codeinterpreter actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeCodeinterpreter · Ayro
What can you do in Codeinterpreter without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Codeinterpreter.
Because the code runs remotely, plt.show() has no display to render into. Scripts write the image to /home/user and Get File returns it instead. The same rule applies to any output worth keeping: write it to a file rather than relying on a rendered cell.
All 5 actions your agent can call on Codeinterpreter, straight from the live MCP connection.
Create a sandbox to execute python code in a Jupyter notebook cell.
Execute python code in a sandbox and return any result, stdout, stderr, and error.
Get a file from the sandbox and returns the file.
Run a command in the terminal and returns the stdout, stderr, and error code.
Upload a file to the sandbox environment.
Same connection, same setup. Pick the next one your team already uses.
Checks whether a service is actually up, acknowledges and escalates open incidents, publishes status page updates, and maintains the on-call rota.
Looks up current Context7 MCP documentation and triggers updates without leaving the conversation.
Answers Gitea configuration questions from the running instance and renders Markdown or AsciiDoc into the HTML Gitea itself would produce.
Reports connection and sync health, issues connect and reconnect sessions, triggers one-off syncs, and proxies authenticated provider calls.
Reports Sauce Labs status, pulls test job history, and confirms supported platforms, tunnel versions, and Appium end-of-life dates.
Shortens a long URL on a public or custom domain mid-conversation, and deletes short links that should no longer resolve.

Authorize the account and your agent has all 5 actions from the first conversation.
