Connect ChatGPT

Implemented from the vendor's documentation dated 2026-10-09. Not yet verified with a real ChatGPT account. OpenAI's pages show no date of their own; 9 October 2026 is the day we read them. The steps below are the ones OpenAI documents. We have not run them. If a step looks different on your screen, trust your screen and tell us. The record for every host is on MCP client compatibility.

What you need

• ChatGPT on the web. OpenAI says the custom server screen is a web feature.
• An account that is allowed to add a custom MCP server. OpenAI's pages do not list which plans can. In a company workspace an owner or administrator may have to allow it first, and workspace rules such as Lockdown apply.
• An Anectico account. You can create it during the sign-in step below.
• Nothing else to set up on our side. ChatGPT calls from OpenAI's servers, so the address must be reachable from the internet, and https://app.anectico.com/mcp is.

Add Anectico

1. Open ChatGPT Plugins (chatgpt.com/plugins).
2. Select the plus button, then Add custom MCP server.
3. Enter a name, for example Anectico. A description is optional.
4. For Server URL, enter https://app.anectico.com/mcp.
5. For authentication, choose OAuth. If ChatGPT asks how it should register with the server, either choice works: Anectico accepts both a client metadata document and dynamic registration.
6. Read the warning that OpenAI shows about trusting a server, and accept it.
7. Select Create as a plugin, then install it.
8. Start a new chat, type @ and choose the plugin.
9. When ChatGPT asks you to connect, sign in to Anectico in the window that opens. You can create your account here. Choose the workspace, uncheck any permission the chat does not need, and select Approve.

If you change anything about the server later, open the plugin's page and refresh the connection. OpenAI documents this after each change.

What works

• Reading. Search for people, issues, logs, traces, replays, alerts, incidents and more, and open the proof page behind an answer. The tool list is the read tools your approval allows.
• Writing does not work from ChatGPT. Anectico allows only read permissions through sign-in. To change something you need a key with write permissions, and OpenAI says ChatGPT does not support custom API keys. This is on purpose and there is nothing to switch on. To make changes, use the CLI or another agent host.
• Confirmation. ChatGPT asks before it runs a tool that is not marked read-only. Every tool you are offered through sign-in is marked read-only.

Try it

Ask the chat:

Search for the most recently active customers and tell me which Anectico tools you used. Do not change anything.

Then ask a question with a real answer, such as:

What happened to buyer@acme.example in the last hour? Cite the evidence and give me a link I can open.

Dots in ChatGPT

OpenAI's Dots connection guide describes connecting installed plugins to a dot. Its MCP Events documentation also names Dots as an MCP-enabled surface. We read these pages on 11 October 2026.

Start with the custom MCP setup above, then check whether the Anectico plugin is available to your dot and workspace. We have not verified Anectico with a real Dots account. An installed ChatGPT plugin is not proof that every Dots account can use it; plan and workspace controls apply.

Limits

• Read-only. See above.
• Tool count. OpenAI's pages do not give a limit. A full read approval offers the read tools of the MCP tool reference, which stays under the sizes in MCP client compatibility.
• Dots and other ChatGPT agent surfaces. Check the connection options above. We have not verified the custom Anectico server on these surfaces.
• A narrower list. Do not add ?profile= to the address. ChatGPT signs in with OAuth and sends the exact address as the resource, so an address with a query string is refused.
• Private installations. If your Anectico runs where OpenAI's servers cannot reach it, ChatGPT cannot connect.

If it does not connect

What you see	What to do
ChatGPT says it cannot reach the server	The address must be public HTTPS and end in /mcp. Open it in a private window: you should get a 401.
The sign-in window never opens	Remove the plugin and add it again, choosing OAuth. Tell us which registration choice it offered.
Sign-in works but ChatGPT says the connection failed	Tell us the time. The most common cause is a resource address that is not exactly https://app.anectico.com/mcp.
The connection works but the tool list is empty	You approved no read permission for the workspace. Disconnect and approve again with the permissions the chat needs.
WORKSPACE_NOT_READY on the first question	Your first workspace is still being prepared. Wait a second and ask again.

To stop ChatGPT's access at any time, revoke the connection under Agents and keys in the Console, or run anectico auth connections revoke. See Revoke an agent's access.