Delivery
The same brain, inside the tools you already open
Claude, Cursor, Claude Code and Codex connect over a remote MCP server with OAuth. ChatGPT connects through the REST API. Slack works in both directions. There is nothing to download.
The problem
Nobody wants a sixth place to go and ask something
The tools your team already uses are the ones they will keep using. A knowledge layer that only pays off inside its own dashboard is a knowledge layer most of the team will forget about.
“What did we decide about refunds over $500?”
Claude
Cursor
SlackThe same question asked in Claude, Cursor, and Slack returns the same answer, because all three read the same company brain.
One answer, one source. Same knowledge, same permissions, wherever it was asked.
What it does
MCP, with OAuth
Claude, Cursor, Claude Code and Codex connect to a remote server exposing 32 read-first tools.
REST, with an API key
ChatGPT through custom actions, or anything else over plain HTTP, against the same service layer and the same permissions.
Slack, both ways
A source it reads from, and a place it answers in, with the answer scoped to whoever actually asked.
One answer, whichever tool asked
The surfaces are different; the brain, the permissions and the sources are not.
- Permission checks run on the same path, including for direct API-key calls
- Claude Code and Codex also sync back, so what you work through in a CLI session is not lost when it ends
- No MCP tool can run a skill: only a person in the Indexbrain chat can do that
The rest of it
Give your AI a company to work for
Connect your tools, and every agent you already use starts the day knowing how your company actually works.