XOi connector

XOi connector

Connect your AI assistant to XOi.

One connector for the parts of XOi your assistant can work with. You choose what each assistant may do in each part.

Connector URL

https://mcp.next.xoeye.com/mcp

What it can do

The connector covers these parts of XOi. When you connect, you choose what the assistant may do in each one.

Feedback

Tell XOi what you need or what went wrong.

  • submit_feedback
    Send XOi a feature request or a bug report, after you agree to the exact text.

How to connect

Add the connector URL to your assistant. Then sign in with your usual XOi account. The assistant acts as you: only in your organization, and only as your role allows.

Claude

  1. Open Settings, then Connectors.
  2. Select Add custom connector.
  3. Paste the connector URL, then sign in to XOi.

Claude Code

Run this command, then sign in to XOi when Claude Code asks.

claude mcp add --transport http xoi https://mcp.next.xoeye.com/mcp

VS Code

Run MCP: Add Server from the Command Palette. Select HTTP, paste the connector URL, then sign in to XOi.

ChatGPT

Add a custom connector in ChatGPT settings. Paste the connector URL, select OAuth, then sign in to XOi.

Security questions

These answers are for XOi administrators and IT and security reviewers.

Does each connection make a new app client in XOi sign-in?

No. When an app registers, this server stores nothing and makes nothing in XOi sign-in (Amazon Cognito). The client ID it returns is a signed record of the app's redirect addresses and name. Every sign-in goes through one fixed sign-in client that XOi owns. That client is confidential: it has its own secret, and only this server holds it. Nothing piles up, so there is nothing to clean up.

Can anyone register a client and use it to phish for consent?

Not from a web page. This server refuses a registration unless each redirect address is one of these:

  • An exact match for a hosted callback of Claude, VS Code, VS Code Insiders and ChatGPT:
    • https://claude.ai/api/mcp/auth_callback
    • https://claude.com/api/mcp/auth_callback
    • https://vscode.dev/redirect
    • https://insiders.vscode.dev/redirect
    • https://chatgpt.com/connector_platform_oauth_redirect
  • A plain http address on the person's own computer (localhost, 127.0.0.1 or ::1).

A web page cannot register its own address. So it can never receive a sign-in code, and consent phishing needs that code. A desktop app on the person's own computer can still use a local address: see Limits we know about. Also:

  • Only public clients can register, with the authorization-code and refresh grants only.
  • Each sign-in must use PKCE with S256. A code is useless without the verifier that only the app has, and it expires after 5 minutes.
  • A client can register at most 10 redirect addresses. Its name is cut to 100 characters, with control characters removed.

Could a fake web page collect refresh tokens?

No. A sign-in code goes only to a registered redirect address, so a web page never gets one. The tokens also give little to steal:

  • This server encrypts the access and refresh tokens it gives out. They work only on this server, not on other XOi APIs.
  • This server never gives out the ID token from XOi sign-in.
  • A refresh token works only for the app that got it, and only here. It lasts at most 30 days.
  • An access token lasts one hour. When it expires, the app must refresh. If an administrator disables the person's XOi account, that refresh fails. So access stops within one hour.

Should this connector use a separate user pool?

It does not need one. A registration makes nothing in XOi sign-in, and the tokens work only on this server. A separate pool would give each person a second XOi account, apart from their organization and role.

What data can the assistant see?

Only what the person can see. This server acts as the signed-in person, in their organization and role, and only in the parts of XOi the person allowed when they connected.

Is registration rate-limited?

Yes. One network address can register 10 clients in one hour.

Limits we know about

  • There is no consent screen for each app yet. The redirect allowlist is what stops consent phishing.
  • A desktop app on your computer can use the local address, as with any desktop sign-in. Connect only apps that you trust.
  • XOi cannot revoke one registered app by itself. To disconnect every app, XOi changes this server's key.

Report a concern

Contact your XOi administrator or XOi support.