Integrations
Remote MCP
Hosted MCP server for Claude, Cursor, and other remote MCP clients.
inis.run exposes a hosted remote MCP server — no local binary, no subprocess. Point your MCP client at our endpoint with your API key and the sandbox tools appear automatically.
Connect to /sse for the MCP event stream. Set MCP_PUBLIC_URL=https://mcp.inis.run when deploying so message endpoints resolve correctly.
Endpoint
https://mcp.inis.run/sseAuthenticate with your API key:
Authorization: Bearer inis_...Configure your MCP client
{
"mcpServers": {
"inis": {
"url": "https://mcp.inis.run/sse",
"headers": {
"Authorization": "Bearer inis_..."
}
}
}
}import { streamText } from "ai";
import { experimental_createMCPClient as createMCPClient } from "ai";
const mcp = await createMCPClient({
transport: {
type: "sse",
url: "https://mcp.inis.run/sse",
headers: { Authorization: `Bearer ${process.env.INIS_API_KEY}` },
},
});
const tools = await mcp.tools();
const result = streamText({
model,
tools,
maxSteps: 5,
// ...
});Works anywhere your agent runs — Vercel, Fly, a container, CI — because nothing needs to be installed on the host.
Tools
| Tool | Description |
|---|---|
execute_code | Stateless Python or Node execution |
create_session | Create a persistent session |
run_command | Shell command in a sandbox |
read_file / write_file | File I/O under /workspace |
expose_port | Expose a guest port → preview URL |
When to use MCP vs SDK
| Use remote MCP when… | Use SDK when… |
|---|---|
| Your runtime supports remote MCP (Cursor, Claude Code, AI SDK) | You need fine-grained session control in app code |
| You want zero integration code and no local install | You are building a custom agent loop |
| Your agent runs in the cloud, not on the user's laptop | You need fork/batch, billing hooks, or custom retry logic |
We do not ship a local stdio MCP server for customers. inisd mcp is operator/dev tooling only.