Skip to main content
This guide walks you through connecting PG:AI to your AI tool of choice. The whole process takes less than 2 minutes.

Step 1: Generate an API Key

1

Open PG:AI Settings

Navigate to Settings → API Keys in your PG:AI dashboard
2

Create a New Key

Click Create API Key and give it a descriptive name (e.g. “Claude MCP” or “Cursor”)
3

Copy the Key

Copy your API key immediately - it won’t be shown again. Keys start with pgai_live_
Keep your API key secure. Anyone with your key can access your PG:AI account data. If you suspect a key has been compromised, revoke it immediately in Settings.

Step 2: Configure Your AI Tool

Claude supports MCP through Connectors (available on Pro and Enterprise plans).
1

Open Settings

Go to Settings → Connectors in Claude.ai
2

Add a Connector

Click Add and select Custom connector
3

Enter the Server URL

https://mcp.pipelinegeneration.ai/sse
4

Set Authentication

Choose Bearer Token and paste your PG:AI API key
5

Save

Click Save - Claude now has access to your PG:AI data

Step 3: Test the Connection

Once connected, try asking your AI tool one of these prompts:

Check Companies

“What companies am I tracking in PG:AI?”

Get Insights

“Tell me about [company name] - what are the latest insights?”

Search Contacts

“Search for VP of Engineering contacts in my PG:AI account”

Generate Content

“Generate meeting prep for my call with [company name]”
If your AI tool responds with company data, insights, or generated content - you’re all set.

Troubleshooting

Double-check the server URL. Make sure you’re using https://mcp.pipelinegeneration.ai/mcp (or /sse for SSE-only clients). Restart your AI tool after updating the configuration.
Verify your API key starts with pgai_live_ and that it hasn’t been revoked. Make sure the Authorization header uses the Bearer prefix.
Your API key may not have the right permissions. Check that it was created with MCP access enabled in Settings → API Keys.
After editing .cursor/mcp.json, reload Cursor (Cmd/Ctrl + Shift + P → “Reload Window”). Check for JSON syntax errors in your configuration file.

Next Steps