MCP connector

What it is

The MCP server is the service that exposes tools; the connector is the record in your client that points to that server and holds the authorisation. One server can have several connectors: one in Claude, one in ChatGPT, one in your editor, each authorised separately.

For a remote server the setup flow is similar everywhere: paste the HTTPS address, give it a name, complete the OAuth sign-in. The client then fetches the tool list from the server; the model decides which tool to call, and when, from those descriptions.

Why it matters

The connector is the only bridge between the chat and your account. Which conversations it is enabled in, which tools appear and how tool calls show up in the thread are all managed on the client side.

Cutting access completely takes two steps: delete the connector in the app and revoke the OAuth grant in the source account. Removing the connector alone does not withdraw the permission you gave.

How Tecrube uses it

Tecrube ships as one connector URL. In Claude go to Settings → Connectors → Add custom connector; in ChatGPT enable developer mode; in Claude Code, Cursor, VS Code and Windsurf add one configuration line pointing to the same address. After the Google sign-in the tool catalogue is available in the chat.

Tools carry annotations stating whether they read or write. Whichever client you connect from, every write action returns a preview first and is never applied without approval, because the gate lives on the server, not in the client.

Example

A marketer adds Tecrube to Claude while a developer pastes the same address into Cursor. Each authorises with their own Google account; account selection and the approval gate behave identically in both, because both talk to the same hosted server.