How it works
Introw exposes an OAuth-protected MCP server that AI clients connect to. You do not flip a switch to turn MCP on; instead, you connect each AI client by pointing it at the Introw MCP server and completing a secure sign-in. Once connected, the client can use Introw’s tools, scoped to your access. The MCP category in Integrations gives you a connector per client, Claude, ChatGPT, and a generic MCP option, each with quick-setup steps and the server URL to copy. The connection uses OAuth, so the client authenticates as you and can be disconnected at any time.Prerequisites
- An AI client that supports MCP, such as Claude, ChatGPT, or Cursor.
- The generic MCP connector requires the MCP connection add-on on your plan; Claude and ChatGPT connectors are available on all plans.
Settings & configuration
MCP connectors live under the MCP category of Integrations.Connectors
Each connector, Claude, ChatGPT, and MCP, opens a configure page with quick-setup steps for that client. Follow the steps in your AI client to add Introw as a connector.MCP server URL
The configure page provides the MCP Server URL to paste into your client. This is the address your AI client connects to; copy it from the page rather than typing it.Connection status
After you complete the OAuth sign-in in your client, the connector shows whether the connection is active. You can disconnect a connector here to revoke a client’s access.Setup walkthrough
Open Integrations
Go to the MCP category of Integrations.
How-to guides
Connect an MCP client
Connect any MCP-capable client - Cursor, Gemini, Windsurf, Notion AI, Lovable, Langdock, and more - to Introw with the generic MCP connector.
Connect ChatGPT
Connect ChatGPT to Introw over MCP so you can query and act on your partner program from inside ChatGPT.
Connect Claude
Connect Claude to Introw over MCP so you can query and act on your partner program from inside Claude.
Partner MCP use cases
What partners can do once they connect their own AI assistant to the partner MCP - and how to drive adoption.
Give partners their own AI assistant
Partners connect their own AI client to the partner MCP from their portal and work with only their own scoped data - no vendor setup required.
Limits & gotchas
Troubleshooting
- The connection shows as not active - complete the OAuth sign-in in your AI client while logged in to Introw.
- The generic MCP connector is locked - it requires the MCP connection add-on on your plan.
- An assistant cannot see expected data - it is scoped to your access; confirm you can see that data in Introw.