Claude Code · Cursor · Any MCP client

Connect Claude and other AI assistants to Pool Runs. Through an MCP server, with keys you control.

Pool Runs runs an MCP server, the standard way AI assistants call outside tools. Give Claude Code, Cursor or your own script a key, and it can look up customers, routes, work orders and invoices, and, if you allow it, add notes or create a work order.

See Demo All integrations

On requestAPI access is turned on for your company when you ask. Then admins create the keys.

Works withMCP clients that can send an Authorization header, like Claude Code and Cursor, or plain JSON-RPC.

What an assistant can reach

Reads by default. Writes only when you say so.

Each tool appears only when the key holds its scope. Read tools return data to the assistant. Write tools only exist on keys made with writes allowed, and only for the actions you picked.

In Pool RunsDirectionIn your assistant

Customers and propertiesSearch, details, tags and status, service historyReadAnswers“Who's on the Henderson account, and when was the last visit?”

Route stopsScheduled and completed, by date or technicianReadCounts and lists“How many stops did Miguel finish last week?”

Work orders, quotes and invoicesStatus, schedule, totals and paymentsReadSummaries“Which invoices are still open from September?”

Customers and notesCreated, edited, noted or archived. A likely duplicate is refused unless you insistWrite, if allowedRequests“Add a note that the Rivera gate code changed”

Work ordersCreated and scheduled for an existing propertyWrite, if allowedRequests“Book a pump repair at the Okafor pool on Thursday”

Also readable

Dashboard, team and pipelines.

Today's numbers from the dashboard, your active team members and roles, and, when pipelines are on for your company, pipelines and their opportunities.

Never exposed

No raw database access.

Free-form queries, table browsing and CSV export are not available to keys, and every answer is limited to your own company's data.

Not yet

Tasks, webhooks, REST.

Tasks can't be reached through a key yet, Pool Runs doesn't send webhooks out, and there's no REST API or Zapier app.

Keys you control

Scoped, expiring and revocable. Checked on every call.

Only an admin or the owner can create keys. Each key is named for what uses it, so you can see which assistant has what and switch one off without touching the others.

Scopes

Pick what it can see.

Choose scopes like customers.view or invoices.view per key. Without a scope, the tools that need it don't appear at all.

Writes

Off unless you turn them on.

Allow write actions one by one. Archiving a customer and deleting an opportunity are flagged as destructive, so clients ask before running them.

Ceiling

Never more than its creator.

A key can't do anything the person who made it can't do today. If their role changes, the key's reach changes with it.

Lifetime

Expire it, or revoke it.

Set a key to expire in 30 days, 90 days or a year, or never. Revoke it from Settings and it stops working at once. Busy keys are rate-limited.

Setting it up

Four steps. The config is written for you.

Once API access is on for your company, an admin or the owner sets up each key from Settings, under API Access (MCP).

01
Ask us to turn it on
API access is switched on per company. Ask during your demo, or contact support if you're a customer.
02
Create a key
Name it for what will use it, pick its scopes, choose any write actions, and set when it expires.
03
Copy it once
The full key is shown one time, with a ready-made client config and a curl command to test it.
04
Add it to your client
Paste the config into an MCP client that supports remote HTTP servers, such as Claude Code or Cursor.

The config Pool Runs writes for youA remote HTTP server with your key in the Authorization header. Pool Runs fills in the key when you create it, and shows a curl command that lists the tools your key can use.

{
  "mcpServers": {
    "poolruns": {
      "type": "http",
      "url": "https://app.poolruns.com/api/mcp",
      "headers": { "Authorization": "Bearer prk_live_…" }
    }
  }
}

MCP and API integration FAQ

Questions about the connection. Plain answers.

Does Pool Runs have an API?

Yes, as an MCP server. MCP (Model Context Protocol) is the standard AI assistants use to call outside tools, and it's plain JSON-RPC over HTTPS, so a script can call it too. There is no separate REST API today. Each tool's exact inputs come back from the server's tools/list call for your key.

Which AI assistants can connect?

Any MCP client that can reach a remote HTTP server and send an Authorization header, such as Claude Code or Cursor. When you create a key, Pool Runs shows a ready-to-paste client config with the key filled in, and a curl command to test it.

Can I add it as a connector in the Claude or ChatGPT app?

Not if the app's custom connector screen only offers an OAuth sign-in. Pool Runs keys are sent in an Authorization header, and there is no OAuth sign-in yet. Use a client that lets you set the header, such as Claude Code or Cursor.

Can an assistant change or delete my data?

Only if you allow it on that key. Keys are read-only unless you turn on write actions and pick which ones. Archiving a customer and deleting an opportunity are marked as destructive, so MCP clients ask before running them. A key can never do more than the person who created it is allowed to do, and that is checked on every request.

Is API access included in my plan?

API access is turned on for your company when you ask. Once it's on, an admin or the owner creates keys from Settings, under API Access (MCP). Ask about it on your demo or contact us if you're already a customer.

Are there webhooks or a Zapier app?

Not yet. Pool Runs doesn't send webhooks out, and there is no Zapier app. To react to something that happens in Pool Runs, poll a read tool on a schedule, or use a workflow inside Pool Runs to send the alert.

Get started

Ask your assistant about the route. With the key you gave it.

Connect Claude Code, Cursor or your own script to Pool Runs with a key that reads only what you allow, and switch it off whenever you want.

See Demo See pricing

API access is turned on per company on request. Keys are created by an admin or the owner.

More integrations

All integrations