External AI agents (MCP)

Connect in one paste

Paste this into Codex, Claude, Cursor, or another agent that supports remote Streamable HTTP MCP servers:

Set up Meshia for me: fetch https://meshia.io/agent-setup.md and follow it.

For Claude Code, the equivalent direct command is:

claude mcp add --scope user --transport http meshia "https://meshia.io/api/mcp"

For Codex CLI:

codex mcp add meshia --url "https://meshia.io/api/mcp"

Authentication

Your agent reuses an existing connection or opens Meshia in your browser. Sign in with the emailed 6-digit code, check the client and account, then click Connect agent. Use Switch account if needed. There is no API key to copy.

Your agent then runs a read-only connection check. A compact receipt confirms the account and workspace access; setup starts no compute and saves no conversation. Your agent first uses a supported MCP refresh when available. If the host still needs a restart or manual setting, it explains the blocker, gives one exact next action and preserves your original task.

Meshia uses OAuth authorization code flow with PKCE. Access tokens are short-lived, refresh tokens rotate, and only credential hashes are stored. Returning clients reconnect without repeating consent while their grant is still active.

To disconnect a client, open Settings → Compute → Connected agents and click Revoke twice. Meshia revokes every active token for that exact client and account.

Optional workspace files

Basic MCP is ready after verification. Your agent then offers Mount files or Skip for now. Mounting installs the same Meshia package with Files access and keeps workspace files available in Finder, Explorer or your Linux file browser. The generated command handles installation, device enrollment and the background service without a second login or pairing-code prompt. Approve the system administrator popup if a filesystem runtime is needed; the installer continues automatically.

Existing installations and permissions are preserved. The mount starts immediately, even before you create a workspace. It starts empty and automatically shows your first workspace's files when you create it. Access all your workspace files locally in your file browser and editor through this network mount. You can also securely attach this computer's compute to a workspace when you choose; compute and conversation syncing are separate opt-ins. Skipping mounting leaves the MCP connection ready to use.

What the agent can control

The MCP server exposes the same canonical controls as the website:

• list, create, inspect, rename, resume, limit, and stop workspaces;
• inspect capacity, request a no-spend quote, attach or release compute, and read utilization;
• run and cancel commands; list, read, edit, move, delete, upload, and download files;
• read and append synchronized workspace messages or ask Meshia's driving agent to take a turn;
• start, inspect, and cancel long-running swarm runs;
• inspect events, statistics, connected machines, teams, members, and invitations.

The external AI can remain the top-level orchestrator while Meshia supplies long-running compute, remote agents, provider tools, and a durable message ledger visible in the workspace UI.

Cost and safety defaults

Workspace creation is deferred and starts no GPU. A good agent should set workspace GPU, hourly, and total limits, inspect availability, and request a quote before asking you to confirm billable attachment.

Meshia requires explicit confirmation fields for GPU attachment, workspace stops, compute release, file deletion, swarm cancellation, invitation emails, and team membership changes. Durable storage is retained by default when compute stops.

Large files

Small reads and edits travel through MCP. For large local uploads, the agent asks Meshia for short-lived file-scoped upload tickets, computes SHA-256 locally, and sends bytes directly to object storage. Downloads page through a compact folder plan that resolves files to content-addressed packs and blocks, each fetched once from object storage with a presigned URL. Pass each page's next cursor unchanged until it is null. Large file bytes do not need to pass through the MCP gateway.

A strong first project

If you already gave your agent a task, it picks up there. If you only asked for setup, it asks what you want to work on or whether you'd like a first-project idea. Suggestions use context you've already shared, propose one concrete outcome, and start with the smallest useful step. A GPU or swarm is suggested only when it helps.

The short setup guide is available as meshia://guide; detailed execution guidance is at agent-guide.md and meshia://operations. Your agent confirms the files or conversation you'll share before saving context, and honors an existing explicit spend authorization or asks you to approve a no-spend quote.