Adding Connect to ChatGPT

Connection facts#

Set it up#

1. Add https://connectbyjbrh.com/mcp as the remote MCP endpoint.

   Result ChatGPT can enumerate the production tool registry.

2. Use a protected private capability.

   Result Connect starts OAuth when authorization is required; sign in and select the intended company.

3. Review the requested scope before consenting.

   Result The grant remains limited to that identity, workspace, selected company and scope set.

Portable package#

Connect's Agent Plugin package contains portable manifests and skills that call the same canonical remote MCP server. It contains no second backend and no secret.

A safe first private test#

1. Ask ChatGPT to read the authorized Connect profile and operational readiness.

   Result A protected read triggers OAuth if needed, and the answer identifies the selected company before any mutation is considered.

2. Ask for a customer by a specific name or address you know belongs to that company.

   Result search_people returns only records inside the authorized reach; no tenant selector is supplied by the model.

3. Ask to create a follow-up with a reason and due interval.

   Result The write records a future obligation and returns its stored row. It does not send a customer communication.

4. Ask for something intentionally outside the v1 surface, such as placing a call.

   Result The connector should say that direct call placement is not exposed rather than reporting an action it could not perform.

Changing or removing access#

A Connect authorization is not permission for every company in the workspace. If work needs to move to another company, use the client's connection/account flow to establish the correct authorization context instead of pasting a tenant identifier into a prompt. The server's protected schemas do not provide that escape hatch. Revoking the OAuth grant or removing the user's live workspace authority stops later protected calls; the package itself stores no secret that needs to be edited.

Write permission is separate from read permission. A user can connect for protected reads without granting configuration or customer-operation changes. When a write is needed, the host can request the additional scope through authorization. This is the preferred test for least privilege: verify that read-only work succeeds while a write call receives an authorization challenge or scope refusal until write access is deliberately granted.

Reviewing marketplace behavior#

A reviewer should distinguish installation from server behavior. Importing the Agent Plugin proves that the manifest is readable. Enumerating the remote endpoint proves the server is reachable. Completing OAuth proves delegated identity. A tenant-scoped read proves isolation. A bounded write plus a cross-company refusal proves that the client is not merely displaying tools but respecting Connect's authority model end to end.

Questions#

Related#

• The Connect MCP server
• Authenticating to the MCP server
• Workspace MCP tools
• Adding Connect to Claude