Stop your coding agent from breaking production.

Connect Claude Code, Cursor, Codex or any MCP client to Polylane, so your agent checks what a change will hit before it writes it.

Your agent checks what calls a service before changing it.

Before it changes a service, your agent sees what calls it, what's failing and what changed recently.

claude · checkout-edge
❯ Lower the Hyperdrive pool to 5 to save connections
polylane · getBlastRadius(hd-prod)
checkout-edge peaks at 41 concurrent queries
orders-api shares the same database
A pool of 5 would make checkout queue at peak.
Keeping 50 and closing idle connections after 30s.
✓ Edited wrangler.toml

Ask your agent what's failing in production, from your editor.

Ask your agent what's wrong. It reads your issues, logs and metrics through Polylane and answers in place.

cursor · orders-api
❯ What's the top issue on orders-api right now?
polylane · listIssues(orders-api)
polylane · queryLogs(orders-api, 1h)
Empty /history responses since 14:52, right after
#1290. The new query filters on customer_id
before the join. Want me to fix it?

Outcomes

Real numbers from Polylane customers.

Add Polylane to your agent.

Claude Code

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "polylane": {
      "type": "http",
      "url": "https://mcp.polylane.com/mcp"
    }
  }
}

Codex

~/.codex/config.toml
[mcp_servers.polylane]
url = "https://mcp.polylane.com/mcp"

Claude Code plugin

The MCP server plus the Polylane skills.

Common questions.

Can my agent change production?

Not unless you allow it. The connection is read-only by default.

Which clients work?

Any MCP client. Sign in with OAuth, or use an API key.

How does my agent sign in?

With OAuth from your MCP client, or with an API key.

What can my agent ask Polylane?

Anything in your workspace: the context graph, issues, logs and metrics, investigations and fixes.

Platform
Surfaces

Nobody should be on-call.