Connect your first integration
What every connector setup has in common, and what differs.
Every connector follows the same shape, whatever the provider.
The two credential models
You generate a key in the provider's console and paste it into PopMCP. Nothing expires unless you revoke it, and there is no callback URL to register.
Most connectors work this way, including Klaviyo, Stripe, Notion, Airtable and Slack.
What you do: create the key, scope it, copy it once, paste it into PopMCP.
The callback URL
OAuth connectors show a callback URL in the connect dialog. Register it in your provider app before you authorize. It must match character for character, because providers reject anything else.
Each integration page shows the exact URL for that connector.
After connecting
PopMCP calls the provider to verify the credential before saving. A connection moves from
PENDING to VERIFIED, or to ERROR with the provider's own message. Only verified
connections get MCP tools.
Some connectors reach several accounts under one authorization, including Google Analytics, Search Console, Google Ads, Xero and Asana. Those show an account picker after you approve, where you choose which accounts to connect and which workspace each belongs to.