MCP

Parlo exposes a hosted remote MCP server at:

1https://parlo.run/mcp

Your agent gets 4 tools: toolList (discover connections and drives), toolSearch (find the right connection/path by intent), toolUse (list/read/stat/write/grep/delete), and codeRun (run TypeScript that orchestrates across connections).

The MCP server uses OAuth, so your agent will ask you to sign in to Parlo before it can access your connections and drives.

Drives in MCP

toolList returns your drives alongside your API connections. toolUse accepts a drive target for list, read, stat, and write operations on R2 drive files:

1{2  "operation": "list",3  "drive": "main",4  "path": "/reports"5}

1{2  "operation": "read",3  "drive": "main",4  "path": "/reports/billing-bug.md"5}

Agents can browse and edit drive files through MCP the same way they access API connections.

Semantic toolSearch

toolSearch uses vector similarity (Cloudflare Vectorize + Workers AI embeddings) to match tools and connections by intent, not just by name. Ask for "billing API" or "issue tracker with labels" and the closest match is returned. Falls back to text matching when no embeddings are available. Tools are auto-indexed when connections are saved.

Gated delete

toolUse supports a delete operation for connections that expose it. Delete is denied by default. To opt in, authorize the MCP client from the OAuth authorize page during the Parlo sign-in flow. The settings page ("Connected apps" section) shows which clients have delete permission granted, and lets you revoke access at any time.

OAuth success page

After authorizing an MCP client such as Cursor, you see a confirmation page before being redirected back to the client. The Parlo settings page has a "Connected apps" section where you can view and revoke authorized MCP clients.

Cursor

One-click install

CLI install

1parlo cursor

This merges Parlo into ~/.cursor/mcp.json and preserves your other MCP servers. Use --project to write to .cursor/mcp.json in the current directory instead.

Manual config

Add to ~/.cursor/mcp.json:

1{2  "mcpServers": {3    "parlo": {4      "url": "https://parlo.run/mcp"5    }6  }7}

Restart Cursor after installing. It will open the Parlo OAuth flow when it needs access.

Claude Code

CLI install

1parlo claude --install

This runs claude mcp add --transport http parlo https://parlo.run/mcp for you.

Manual install

1claude mcp add --transport http parlo https://parlo.run/mcp

Or the JSON form:

1claude mcp add-json parlo '{"type":"http","url":"https://parlo.run/mcp"}'

Start or restart Claude Code and complete the Parlo OAuth flow in your browser when prompted.

Useful checks:

1claude mcp list2claude mcp get parlo

Codex

CLI install

1parlo codex --install

If the codex CLI is available, this runs codex mcp add parlo --url https://parlo.run/mcp. Otherwise, it appends the config to ~/.codex/config.toml.

To authenticate after installing:

1parlo codex --login

Manual config

Add to ~/.codex/config.toml:

1[mcp_servers.parlo]2url = "https://parlo.run/mcp"

Then authenticate:

1codex mcp login parlo

Restart Codex after changing MCP configuration.

OpenCode

CLI install

1parlo opencode --install

This writes the Parlo MCP config to opencode.json in the current directory.

To authenticate after installing:

1parlo opencode --login

Manual config

Add to opencode.json:

1{2  "$schema": "https://opencode.ai/config.json",3  "mcp": {4    "parlo": {5      "type": "remote",6      "url": "https://parlo.run/mcp",7      "enabled": true8    }9  }10}

Then authenticate:

1opencode mcp auth parlo

Other agents

For any agent not listed above:

1parlo agent <name>

This prints the MCP config in both JSON and TOML formats. The MCP server URL is always https://parlo.run/mcp.

Verify access

Once installed, ask your agent:

1Use Parlo to list my connections.

A healthy install should discover the Parlo MCP tools, prompt for OAuth if needed, and return your connections and drives.

Try these follow-up prompts:

1Use Parlo to read the README for my GitHub connection.

1Use Parlo codeRun to count how many active connections I have.