MCP Quickstart

This guide gets you connected to the hosted PG:AI MCP server at https://mcp.getpg.ai. Most users connect Claude with OAuth; developers often use an API key in Cursor or scripts.

Before you start

A PG:AI account with access to at least one organisation
For Claude: a plan that supports Connectors (Pro, Team, or Enterprise)
For API key auth: permission to create keys in Settings → API Keys

Option A - Claude (recommended)

Claude connects through a Custom connector and signs in with your PG:AI identity (OAuth). Your organisation is resolved automatically from your PG:AI user email - you do not paste an org ID into Claude.

Step 1: Open Connectors in Claude

Open Claude.ai and sign in.
Go to Settings (profile menu → Settings).
Open Connectors (sometimes under Integrations depending on your plan).

Screenshot needed: Claude Settings → Connectors page with the Add connector button visible.

Step 2: Add the PG:AI connector

Click Add connector (or Add custom connector).
Enter a name, for example PG:AI.
Enter the server URL:

https://mcp.getpg.ai/mcp

If your Claude build only supports SSE connectors, use:

https://mcp.getpg.ai/sse

Save the connector.

Screenshot needed: The “Add custom connector” form filled in with name PG:AI and URL https://mcp.getpg.ai/mcp.

Claude will prompt you to authenticate.
Complete the PG:AI / Auth0 login with the same email as your PG:AI workspace user.
Approve access when asked.

Your PG:AI account email must match your login email. Org membership is resolved server-side - if login succeeds but tools return no data, check that your user exists in the correct organisation in PG:AI.

Screenshot needed: OAuth consent / PG:AI login screen during connector authorisation.

Step 4: Enable the connector in a chat

Start a new chat in Claude.
Open the + or tools menu near the message box.
Enable the PG:AI connector for that conversation.

Screenshot needed: New chat with the PG:AI connector toggled on in the tools/connectors menu.

Step 5: Verify it works

Try these prompts in order:

Prompt	Expected behaviour
”List my tracked accounts”	Calls `accounts` - returns companies in your territory or org
”Get the company profile overview for Salesforce”	Calls `company` with `include: ["overview"]`
”What templates can I use to generate content?”	Calls `templates` - lists canvas and sequence recipes

If Claude says it cannot reach PG:AI or authentication failed, see Troubleshooting below.

Claude Team / Enterprise

An admin can add the same connector once under Admin settings → Connectors. Each user still connects with their own PG:AI login so data stays scoped to their organisation membership.

Option B - API key (Cursor, scripts, other clients)

Use this when OAuth is not available (for example Cursor or local testing).

Step 1: Create an API key

Open Settings

In PG:AI go to Settings → API Keys

Create a key

Click Create API Key. Name it (e.g. “Cursor MCP”). Enable MCP scopes if prompted.

Copy the key

Copy the key immediately - it starts with pgai_live_ and is only shown once.

Screenshot needed: PG:AI Settings → API Keys with Create API Key and scope selection visible.

Treat API keys like passwords. Revoke compromised keys in Settings immediately.

Step 2: Configure Cursor

Create or edit .cursor/mcp.json in your project (or add via Cursor Settings → MCP):

{
  "mcpServers": {
    "pgai": {
      "url": "https://mcp.getpg.ai/mcp",
      "headers": {
        "x-api-key": "pgai_live_YOUR_KEY_HERE"
      }
    }
  }
}

You can also use Authorization: Bearer pgai_live_YOUR_KEY_HERE instead of x-api-key. Reload Cursor (Cmd/Ctrl + Shift + P → Developer: Reload Window). You should see pgai as a connected MCP server.

Step 3: Verify with tools/list

Any MCP client can list tools with a JSON-RPC tools/list call. Example with curl:

curl -s -X POST https://mcp.getpg.ai/mcp \
  -H "x-api-key: pgai_live_YOUR_KEY" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

You should see tools such as company, search, accounts, and templates.

Connection details (reference)

Setting	Value
Streamable HTTP URL	`https://mcp.getpg.ai/mcp`
SSE URL	`https://mcp.getpg.ai/sse`
OAuth metadata	`https://mcp.getpg.ai/.well-known/oauth-protected-resource`
API key header	`x-api-key: pgai_live_…` or `Authorization: Bearer pgai_live_…`

Troubleshooting

Claude says authentication failed

Confirm you completed OAuth with the same email as your PG:AI user.
Try removing and re-adding the connector.
For Team/Enterprise, confirm an admin enabled custom connectors.

Tools return 401 or authentication required

API key: check the key starts with pgai_live_ and was not revoked.
Claude: ensure the connector is enabled for the current chat.

Connector added but Claude never calls PG:AI

Enable the connector in the chat’s tools menu (not only in Settings).
Ask a PG:AI-specific question: “Use PG:AI to list my accounts”.

templates returns an error

Template discovery depends on the Data Hub and Xano template routes. If you see a UUID validation error, contact support - this is a known routing issue being fixed on the backend.

Cursor does not show pgai

Reload the window after editing mcp.json.
Check JSON syntax and that the URL has no trailing slash issues.

Async jobs never finish

Generation and enrichment are asynchronous. After template_generate, companies_add, or contact_find_email_phone, poll get_operation_status every few seconds until status is completed or failed.

Next steps

Tools reference

All 22 tools and parameters

Examples

Prompts for research, contacts, and generation

Resources

Passive company and territory lists

Overview

Endpoint Guides

MCP Server

Before you start

Option A - Claude (recommended)

Step 1: Open Connectors in Claude

Step 2: Add the PG:AI connector

Step 4: Enable the connector in a chat

Step 5: Verify it works

Claude Team / Enterprise

Option B - API key (Cursor, scripts, other clients)

Step 1: Create an API key

Step 2: Configure Cursor

Step 3: Verify with tools/list

Connection details (reference)

Troubleshooting

Next steps

Tools reference

Examples

Resources

​Before you start

​Option A - Claude (recommended)

​Step 1: Open Connectors in Claude

​Step 2: Add the PG:AI connector

​Step 3: Sign in with PG:AI

​Step 4: Enable the connector in a chat

​Step 5: Verify it works

​Claude Team / Enterprise

​Option B - API key (Cursor, scripts, other clients)

​Step 1: Create an API key

​Step 2: Configure Cursor

​Step 3: Verify with tools/list

​Connection details (reference)

​Troubleshooting

​Next steps

Tools reference

Examples

Resources

Before you start

Option A - Claude (recommended)

Step 1: Open Connectors in Claude

Step 2: Add the PG:AI connector

Step 3: Sign in with PG:AI

Step 4: Enable the connector in a chat

Step 5: Verify it works

Claude Team / Enterprise

Option B - API key (Cursor, scripts, other clients)

Step 1: Create an API key

Step 2: Configure Cursor

Step 3: Verify with tools/list

Connection details (reference)

Troubleshooting

Next steps