Connect ChatGPT
Add Tabba to ChatGPT as a custom MCP connector.
ChatGPT reaches a remote MCP server through a custom connector that you add by its URL. In ChatGPT that sits behind developer mode, and in a workspace an admin may have to allow it before you can start.
Check what your ChatGPT offers first
Which ChatGPT plans offer custom MCP connectors, and where the settings are, is OpenAI's to say and changes. Their own documentation of developer mode has the current steps. The steps below state what Tabba needs from them.
1. Turn on developer mode
Turn on developer mode in your ChatGPT settings. In a workspace, an owner may have to allow custom MCP connectors first. Until they do, the setting is not there to find.
2. Add the server
Create a custom connector and give it:
- URL:
https://www.tabba.io/api/mcp, including the/api/mcppath - Authentication: OAuth
https://www.tabba.io/api/mcpLeave any client id and client secret fields empty: ChatGPT registers itself with Tabba. It then opens Tabba in your browser. Sign in if you are asked to, pick the company on the consent page, and choose Approve.
3. Use it
Enable the connector for a conversation, then ask in plain language:
Using Tabba, what work do I have open?ChatGPT should call get_my_work and answer with your open lines. A read
answers from the work you hold a place on, and a list opens by saying which
view produced it. The whole company is an admin's and an auditor's to ask
for. See
Auth and scopes.
The tool list ChatGPT shows for the connector is the one Tabba built for your connection: it follows the scope of the token and your role in the company. If ChatGPT keeps a copy of the list, refresh it after you connect again or after your role changes. Otherwise it may offer a tool the server no longer registers for you, and that call fails.
What to expect on writes
ChatGPT gets the same contract as every other client: a plan_* tool answers
a written plan, and nothing changes until commit is called after you
confirm. A standard user is offered plan_register_work and commit, and an
auditor neither. The other plan tools are an admin's. See
Plan and commit.
Tabba has no search or fetch tool
A ChatGPT feature that works only through a connector's search and
fetch tools cannot use Tabba: the server registers neither. Its read
tools are typed questions about your Sales data, not a document index. Use
a normal chat when you want Tabba to answer or to plan a change.
Troubleshooting
- There is no developer mode setting. The workspace has not allowed it. An owner does that in the workspace's settings.
- The connector fails to connect. Check that the URL ends in
/api/mcp.https://www.tabba.ioalone is the OAuth issuer, not the MCP endpoint, and does not answer a tool call. - A tool is missing, or one you no longer have is still offered. Refresh the connector's tool list. The catalogue is built per request from your token's scope and your role.
- It answers from memory and calls no tool. Name the connector in your message ("using Tabba") and check that it is enabled for the conversation.
- A write did not happen. A plan is not a commit. Confirm the plan in so
many words. If the conversation moved on, the plan may have run out: a plan
lives fifteen minutes, after which the commit is answered
PROPOSAL_EXPIREDand the plan tool is called again.
Remove it
Remove the connector in ChatGPT, then revoke the access in Tabba: under Claude and other AI clients on your profile settings, choose Revoke access. That ends every AI client connection of yours, not only this one.