Connect ChatGPT
Add Siglata to ChatGPT as a custom MCP server, install the plugin and sign in.
On ChatGPT Business, an admin or owner creates and publishes the Siglata plugin once for the workspace. Each member then installs the plugin and signs in to Siglata. A dot uses that connection, not setup text pasted into a conversation.
The steps follow OpenAI’s guide to custom MCP servers. Workspace permissions decide whether the option appears. On Business and Enterprise, an admin adds it once for the team; on other plans, each person adds it, if the option shows up in their account. In a November 2026 test on a Pro account, the option was there and the plugin got every Siglata tool, writes included, although OpenAI’s help mentions only reads on Pro.
Admin: create the plugin
On a personal plan, use your own account and skip workspace selection and the role check in step 1.
-
Open ChatGPT on the web and select the company’s workspace. Check your role under Workspace settings → Members: on Business, you must be an Admin or Owner. If you are a member, send this page to the admin and wait for publication before continuing.
-
Open Plugins, click + and then Add custom MCP server. You do not need to enable Developer Mode in this interface.
-
Name it
Siglataand paste the address under Connection:https://www.siglata.com/v1/mcp -
Under authentication, choose OAuth, read the warning, check I understand and want to continue and click Create as a plugin.
-
Check the discovered tools. The plugin can read and change the company’s files and records; review the write tools before publishing too. If testing asks you to authenticate, sign in to Siglata and pick the right company. This does not install the plugin on other members’ accounts.
On a personal plan, skip publication: find Siglata in your personal plugins and install it. Continue at step 3 of Each member: install and sign in, to sign in to Siglata.
Business and Enterprise/Edu
Admin: publish to the workspace
In Admin Console, select the company’s workspace and open Plugins → Manage Legacy Apps → Drafts. Find Siglata, click Publish and review the safety warnings, including those for write actions. Publication adds Siglata to the workspace’s approved plugins. Do not create a separate plugin for each member.
This is the custom-app publication path OpenAI documents. If Manage Legacy Apps, Drafts or Publish is missing, stop at that step: confirm the workspace and your admin role. Creating a draft does not count as publication.
On Enterprise/Edu, admins and owners can also use RBAC to give other members permission to create connections to custom MCP servers. Only admins and owners publish to the workspace.
Each member: install and sign in
- On the ChatGPT account that will use Siglata, select the same workspace and open Settings → Plugins.
- Find Siglata among the approved plugins and install it. If it is missing, ask the admin to check publication and that account’s access.
- Sign in to your Siglata account, pick the company and authorize. Publishing the plugin does not automatically connect each member’s Siglata account.
- In a new conversation, type
@, pick Siglata and ask: “Check the company office and tell me whether it is ready for work.” Check that theoffice_statuscall completed and returned the right company. The authorization screen alone does not prove it works.
When people use the same login
If people already use one ChatGPT login, setup on that account means one install, one Siglata sign-in and one dot. Everyone uses the same identity and the access of the person who signed in to Siglata; History does not distinguish who was using that login. This describes shared setup, not a recommendation to share credentials. With separate logins, each member installs and signs in separately.
Dots
- Finish publication, installation and sign-in on the ChatGPT account the dot uses, as in the steps.
- Open that account’s dot and ask: “Check the company office and tell me whether it is ready for work.”
- In the dot itself, check for a completed
office_statuscall returning the right company. If the office is still being prepared, wait and check again. A call in the desktop app or an ordinary conversation does not prove the dot is connected. - After that result, ask it to do the work, for example “Save a short note to Files.” Its changes are recorded under ChatGPT and the person who signed in to Siglata.
Pasting the setup message or SKILL.md does not install the plugin or authorize the dot. It has no MCP setting of its own and does not read the computer’s config.toml. Without the plugin tools, stop and return to the admin step; do not try calling the server address directly or paste passwords or tokens into the conversation.
What was checked
On November 13, 2026, the creation and publication steps were checked against OpenAI’s documentation. The browser available for this check was signed out of ChatGPT; there was no access to a Business workspace with an admin role or to a connected dot. Business publication and the dot’s tool call still need that check. A desktop or Pro account test did not verify them.
Desktop app
If your account already has the Siglata plugin installed, start with it. The installation and sign-in steps also serve dots. In the Codex conversation in the desktop app, check that Siglata’s tools appear and ask for a real call to office_status. Continue only when the tool returns active for the right company in that conversation. If the plugin tools are already available there, do not add another connection in ~/.codex/config.toml.
If your account does not have the plugin, use the Codex steps as a fallback to configure the MCP server in ~/.codex/config.toml. Check the tools and the office_status result in the conversation where you will work.
As of November 13, 2026, the available check confirmed the plugin tools and office_status returning active only in the Codex runtime bundled with the app, with a fresh CODEX_HOME and no config.toml. That test does not confirm that it works in the app’s window, which remains unverified.
Approvals
ChatGPT lists every tool without the readOnlyHint annotation under Write. With the plugin’s default permission, Allow low-risk tools, it decides call by call which ones to confirm: it may save a file without asking, and ask Allow once before it adds a row to a table. A dot follows its own approval rules. Choose Always allow only if you trust the plugin.
Done
Setup is complete only when a real call to the office_status MCP tool returns active for the right company. Ask ChatGPT to call the tool. Success in the browser doesn’t confirm that the office is ready. To use a dot, check that result in the dot itself. Then add files when you need to.
Troubleshooting
- No Add custom MCP server option. Workspace permissions or the account’s security restrictions don’t allow custom servers; on Business and Enterprise, ask an admin. Use Codex, which comes with every ChatGPT plan.
- Wrong organization. Remove the plugin, create it again and pick the right company at sign-in.
- No tools. Check that the plugin is installed and pick Siglata with
@in the chat. - HTTP 401 or you only pasted SKILL.md. The direct address does not sign you in. Stop retrying and follow this page’s publication, installation and sign-in steps. Never paste a token into the conversation.
FAQ
Does Siglata work on ChatGPT Plus or the free plan?
If the “Add custom MCP server” option shows up under Plugins in your account, yes: follow the steps above. On Business and Enterprise, an admin adds it once for the team. Codex is included in every ChatGPT plan, Free and Go included, and connects to Siglata with one command.
Does Siglata work in the ChatGPT mobile app?
No. As of October 2026, OpenAI says custom MCP servers work in ChatGPT on the web.