Personal ChatGPT plans connect to Tindre with a personal access token. Business and Enterprise workspaces can publish a custom MCP connector under their workspace policy.
- 1
Create a Tindre token
Under Settings → API & MCP, create a named personal access token and copy it once.
- 2
Enable developer mode
In ChatGPT, open Settings → Connectors → Advanced and turn on Developer mode.
- 3
Add the connector
Paste the MCP address, choose token authentication, and paste the token.
- 4
Enable it for the chat
Turn on the connector when the conversation should use Tindre.
The token acts as you
It has no independent scope selector. Every request uses your live Tindre permissions and Role visibility. Revoke it immediately if exposed.
Writes on personal plans
MCP write actions are not verified for personal Plus or Pro plans. Search and reads can still work, while changes may be unavailable. Tindre writes that require confirmation never bypass that requirement.
Business and Enterprise
A workspace administrator allows custom MCP connectors under Permissions & Roles → Connected Data, creates and tests the connector as a draft, then publishes it. On Business a published connector is on for everyone by default; on Enterprise and Edu it starts off and is opened through RBAC. Each user should authenticate as themselves; do not distribute one shared credential.
Verify disclosure
Tindre tool results become part of the ChatGPT conversation context. Complete the provider and data review before enabling the connector broadly.