Pick up the thread.
Search meeting evidence and project documents. Get source references alongside the context.
YOUR TEAM’S SHARED CONTEXT
A shared brain.
In your own tools.
One place for what we know. A connection to the AI tools you already use.
We’re building shared company knowledge for Xcubator. Start by connecting your tool and verifying your Microsoft sign-in.
MCP One endpoint. Your Microsoft account.
Ideas become connected.
XC / SHARED INTELLIGENCEConnection test is ready.
Microsoft sign-in and connection_status are available now. Meeting import and semantic search are prepared; teammate access is awaiting the employee group configuration.
01 / GET CONNECTED
Your tool. Our context.
Choose your client below.
You’ll need your Xcubator Microsoft account.
MCP SERVER URL
https://brain.xcubator.de/mcpConnect from the desktop app
● CLI sign-in verifiedUsing the MCPs → Connect to a custom MCP screen? Start here. The desktop form and CLI configuration are two ways to configure the same connection. Desktop-only sign-in has not yet been verified for Brain.
Choose Streamable HTTP
In the MCPs tab, open the custom MCP form. Set Type to Streamable HTTP. Brain runs at a URL; the STDIO command, arguments and environment-variable fields are for locally launched servers.
- Name
xcubator-brain- Type
- Streamable HTTP
- URL
https://brain.xcubator.de/mcp
Configure Microsoft sign-in
Brain uses a pre-registered Microsoft OAuth client. A URL alone may not complete setup. If the HTTP form exposes an OAuth client ID, use
14b78d29-da3e-4caa-912b-3d8b2c30bac0. If it does not expose the required OAuth settings, save the server and update its existing configuration using the exact settings below. Do not create a duplicate entry.Leave manually supplied bearer tokens and HTTP headers empty. Authenticate with your Microsoft account instead.
Restart and authenticate
After saving the complete configuration, restart the MCP connection and select Authenticate if offered. The tested CLI sign-in below is available as a fallback. Use
/mcpto inspect the connection, then try the test prompt.
Desktop transport fields checked against the current app screen; restart and authentication flow checked against official OpenAI documentation on 27 October 2026.
Exact configuration / CLI fallback
These are the settings used for the verified Codex sign-in. The desktop app and CLI share local configuration. If your desktop app uses a different computer or execution environment, apply the configuration there.
Add the server configuration
Open
~/.codex/config.toml. Add the following, preserving your other settings. If this server already exists, update its section instead of adding it twice.config.toml[mcp_servers.xcubator-brain] url = "https://brain.xcubator.de/mcp" scopes = ["https://brain.xcubator.de/mcp/knowledge.read", "offline_access"] [mcp_servers.xcubator-brain.oauth] client_id = "14b78d29-da3e-4caa-912b-3d8b2c30bac0" callback_port = 8766 callback_url = "http://localhost:8766/callback/mmozU5mDYW1c"Sign in with Microsoft
Run this in the terminal on the computer where Codex is installed.
Terminalcodex mcp login xcubator-brain --scopes https://brain.xcubator.de/mcp/knowledge.read,offline_accessUsing SSH or a remote server?
Use the URL-based flow below. Open the Microsoft URL it prints, sign in, then paste the full resulting callback URL into the terminal’s hidden prompt and press Enter. The localhost page does not need to load. Do not paste that URL into a chat or ticket.
Remote terminalcodex mcp login xcubator-brain --no-browser --scopes https://brain.xcubator.de/mcp/knowledge.read,offline_accessTry the connection
Start a new Codex session or reload its MCP connections, then use the test prompt below.
Connect with Claude Code
Client test pendingThe registration is prepared. This guide has not yet been verified with a complete Claude Code sign-in.
Register the remote server
Run this with a current Claude Code CLI. User scope makes the connection available across your projects.
Terminalclaude mcp add --transport http --scope user \ --client-id 14b78d29-da3e-4caa-912b-3d8b2c30bac0 \ --callback-port 8765 \ xcubator-brain https://brain.xcubator.de/mcpSign in
Terminalclaude mcp login xcubator-brainFor a remote terminal, add
--no-browserand follow the hidden callback prompt. The registered callback uses port 8765.Open Claude Code and test
Use
/mcpto check the connection, then send the test prompt below.
Connect with ChatGPT web
Admin setup requiredThis section is for hosted ChatGPT web. If you see a desktop form with STDIO and Streamable HTTP, use the Desktop / CLI tab instead. Hosted ChatGPT needs its own HTTPS callback registered in Microsoft Entra. This connection has not been tested yet; availability depends on your account and workspace permissions.
Create a custom MCP connection
In ChatGPT, open Plugins → + → Add custom MCP server. Some interfaces show Settings → Apps → Create; developer mode or administrator access may be required.
Enter the connection details
- Name
- Xcubator Brain
- Server URL
https://brain.xcubator.de/mcp- Authentication
- OAuth
- Advanced registration
- User-Defined OAuth Client
- Client ID
14b78d29-da3e-4caa-912b-3d8b2c30bac0
Ask an administrator to register the callback
Copy the Callback URL shown in the setup form and share it with the Xcubator Brain administrator. They must configure the matching Entra redirect and any required client credentials before you finish connecting. Keep existing Codex and Claude redirects.
This setup URL is different from a post-login URL containing an authorization code. Never share post-login codes or client secrets in chat.
Complete sign-in and scan tools
After the administrator confirms configuration, finish Microsoft sign-in and scan the tools. Select Xcubator Brain in a new chat and use the test prompt below.
02 / MAKE YOUR FIRST CONNECTION
Say hello
to your shared brain.
Ask your connected AI client to run this prompt. A successful response confirms that Microsoft sign-in and the MCP connection work.
EXPECTED RESULT
authenticated: true
knowledgeAvailable: falseThe second value is expected until your team’s access group is configured.
TRY THIS NOW
Call Xcubator Brain’s connection_status tool and tell me whether I’m connected.
Read-only connection check
03 / WHAT WE’RE BUILDING
Less catching up.
More moving forward.
Planned workflows—not available yet.
Access will be scoped to your projects.
See what changed.
Compare discussions over time and distinguish proposals, decisions and open questions.
Keep the useful parts.
Explicitly save documents or draft concepts, with provenance and review permissions.
A FEW GOOD QUESTIONS
Before you dive in.
Why does sign-in redirect to localhost?
That callback delivers the sign-in result to your AI client. The MCP service itself stays at brain.xcubator.de. If your browser and client run on different machines, use the no-browser flow and paste the full callback URL into the terminal’s hidden prompt.
Microsoft reports a redirect mismatch.
Your client must use the exact registered callback and port. Share the error code and the callback address without its query string with your administrator. Never send the URL’s code or state parameters. Different client versions may generate a different callback.
I’m signed in, but I can’t search documents.
Without a source grant, only connection_status is exposed. Meeting search and retrieval are prepared, but the employee group must be configured first. Signing in alone does not grant access to meeting content.
Will Brain capture my conversations automatically?
No automatic session capture is enabled. Planned saving workflows require an explicit request or an approved project policy. Never upload credentials or unrelated personal conversations.
Does the client ID need to stay secret?
No. The client ID identifies the Microsoft app and is public configuration. Passwords, client secrets, tokens and post-login callback URLs must stay private.