Skip to main content
The Model Context Protocol (MCP) is an open standard for connecting AI agents to external tools and data sources. For most users, Sapt uses one connector URL:
Add that URL to Claude or ChatGPT, sign in with your Sapt account, and the available tools show up for the Projects you can access.

​
Claude setup

  1. Open Claude connectors.
  2. Click Add custom connector.
  3. Name it Sapt.
  4. Paste the Sapt MCP URL:
  1. Click Connect and authorize with your Sapt account.
  2. Optional but recommended: set tools to Always allow.

​
ChatGPT setup

  1. Open ChatGPT connector settings.
  2. Go to Settings → Apps → Advanced settings.
  3. Turn on Developer mode.
  4. Click Create app.
  5. Name it Sapt.
  6. Paste the Sapt MCP URL:
  1. Set authentication to OAuth.
  2. Check the disclaimer and click Create.

​
Authentication

Claude and ChatGPT use OAuth. When the client asks you to connect, sign in with your Sapt account. The connector uses your account permissions to decide which Projects and tools are available. API keys are for direct REST API usage and server-side integrations, not the normal Claude or ChatGPT connector flow.

​
Tools

The connector exposes Sapt capabilities across Project context, memory, CRM, content, social, ads, email, reviews, analytics, and setup. Every signed-in session sees the same tools; a tool used in a Project without the integration it needs says what is missing. Your account permissions decide which Projects and actions the tools can reach. Most people only need the main connector. A few narrower connectors carry a focused slice of the same tools, for clients that want a smaller tool list: The old Leads, CRM, CMS, Builder, Google Business Profile (/gbp), and SERP connector URLs now answer as the main Sapt connector. See Leads tools.

​
MCP or REST?

Both let software work with the same Project. Pick by how you’re building.

​
Safety basics

Technical access should be scoped and intentional.
  • Keep API keys on the right Project.
  • Enable tools only where they’re needed.
  • Use review steps for public or customer-facing actions.
  • Keep secrets in environment variables or secure app settings.
When in doubt, start with read-only or draft-producing access before allowing direct changes.