inis.run
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/sse

Authenticate 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

ToolDescription
execute_codeStateless Python or Node execution
create_sessionCreate a persistent session
run_commandShell command in a sandbox
read_file / write_fileFile I/O under /workspace
expose_portExpose 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 installYou are building a custom agent loop
Your agent runs in the cloud, not on the user's laptopYou 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.

On this page