VORIM
We use cookies

We use cookies to analyze site traffic and improve your experience. You can choose to accept all cookies or only essential ones. See our Privacy Policy.

Remote MCP: ChatGPT, OpenAI Dots and Instinct

Connect Vorim to ChatGPT, OpenAI Dots or any app that supports remote MCP servers. Paste one URL, sign in to Vorim and choose what the app may do; no API key is copied anywhere.

Remote MCP: ChatGPT, OpenAI Dots and Instinct

Vorim runs a hosted MCP server at https://api.vorim.ai/mcp. Apps that connect to remote MCP servers over HTTPS add it with that URL and sign in through OAuth, so you never paste an API key into them. When you approve the connection, Vorim creates an API key for your organisation that only that app holds, limited to the permissions you tick.

MCP server URL:  https://api.vorim.ai/mcp
Authentication:  OAuth (the app registers itself; nothing to fill in)
text

ChatGPT and OpenAI Dots

Dots use the apps connected to your ChatGPT account and have no separate MCP setting, so you add Vorim once in ChatGPT and your Dots can use it too.

  1. In ChatGPT, open Settings, find the advanced connector settings and turn on Developer mode. OpenAI has moved this toggle more than once; on business plans a workspace admin may need to allow custom connectors first.
  2. Create a connector. Name it Vorim, paste https://api.vorim.ai/mcp as the URL, choose OAuth and confirm the warning about custom connectors.
  3. ChatGPT sends you to vorim.ai. Sign in, check which permissions to grant and press Approve. Only owners, admins and developers can approve.
  4. Ask ChatGPT, or a Dot, to use Vorim. It registers itself as an agent once, asks Vorim before anything with side effects and records what it did.

Which plans include Developer mode and Dots changes over time; check OpenAI's help centre for yours.

Instinct and other apps

Any app that can add a remote MCP server with OAuth works the same way. As of October 2026 Instinct does not publicly document custom MCP connectors; if your Instinct account offers one, add the URL above and approve it. Apps that only accept a fixed bearer token cannot use this endpoint yet; use the local server (npx -y @vorim/mcp-server with an API key) where they support it.

Tools

  • vorim_whoami shows the organisation and the permissions this connection holds.
  • vorim_register_self gives the assistant its own agent identity (its private key is never returned to the chat).
  • vorim_check_action asks Vorim whether an action may go ahead: allow, deny or escalate to a person. vorim_get_decision reads the outcome of an escalation.
  • vorim_log_action writes a signed audit event after the action.
  • vorim_list_agents, vorim_check_permission and vorim_verify_trust read state.

A good custom instruction for the assistant is to check with Vorim before booking, paying, sending or deleting anything, and to log the result afterwards.

What the app can and cannot do

The grantable permissions are agents:read, agents:write, permissions:read, audit:read, audit:write and runtime:decide. A connected app never receives runtime:manage or API-key permissions, so it cannot change rules, budgets or keys, or undo a suspension. Access tokens last an hour and refresh tokens rotate; reusing an old code or refresh token cuts the whole connection off. Connectors, then Connected apps, lists every app with a Disconnect button that revokes its tokens and its key at once.

Need Help?

Book a demo for a walkthrough, or contact us for support. For enterprise needs, reach out at sales@vorim.ai.