MCP connector
An MCP connector is the configuration inside an AI client — such as Claude or ChatGPT — that links the assistant to a specific MCP server, making the tools that server exposes available inside the conversation.
It helps to separate two things people often merge. The MCP server is the service that exposes tools. The connector is the entry inside your AI client that points at that server. One server can have many connectors — one in Claude, one in ChatGPT, one in an IDE — and each is authorized separately. In Claude they live under Settings → Connectors; other MCP-compatible apps have a connectors or apps screen, and developer tools use a config file.
Adding a remote connector follows the same pattern everywhere: paste the HTTPS URL, name it, and complete the OAuth sign-in that opens. The client then performs a handshake and pulls the server's tool list — every tool's name, description and parameter schema. The model decides which tool to call, and when, by reading those descriptions. That is why clear tool naming and annotations matter as much as the underlying functionality.
A few operational details are worth knowing. Connectors can usually be enabled or disabled per conversation or per project, so you are not exposing every tool in every chat. Tool calls appear in the transcript, so you can see exactly what ran and with what arguments. And to fully cut access you need two steps: remove the connector in the app, and revoke the OAuth grant in the source account. Availability of remote connectors can also vary by AI app and plan.
Opus Growth ships as a single connector URL — mcp.opus-growth.com — that works in Claude, ChatGPT and any other MCP-compatible app. After the Google sign-in, the connector's 221-tool catalogue appears in the chat — with Meta Ads and Business Profile still closed until their platform approvals clear. Each tool is annotated as read-only or write so the client can label it correctly, and every write is returned as a dry-run preview before it is applied.
Frequently asked questions
No. The server is the remote service that provides the tools; the connector is the record in your AI client that points to it and holds the authorization. The same server can be connected from several clients at once.
Yes, if the server is remote and both apps support remote MCP. You use the same URL in each app, but you complete a separate OAuth sign-in per app.
Delete it in your app's connector settings, then revoke the OAuth grant in the source account — for example in your Google account permissions. Removing only the connector leaves the token grant in place.
