Connect your own AI (MCP)
Work on your company from the AI tools you already use. Claude Code, Codex, Cursor and any other app that speaks MCP (the Model Context Protocol) can read your company's memory, see and create tasks, and hand work to your agents.
What it's good for
- Ask your company from your editor. "What did we decide about pricing?" reads the answer from your company's memory.
- File work where the team sees it. Create a task for Kai from Claude Code, and it shows up on the Team page.
- Keep what you learn. Store a decision or a lesson back into memory, so your agents know it too.
Connect in three steps
- In AEQI, open Account settings › Access › API keys and press Manage keys.
- Create a key for one company and give it a name. It is shown once, so copy it.
- Copy the command AEQI shows you, with your company already filled in, and run it. For Claude Code it looks like this:
claude mcp add aeqi --transport http https://app.aeqi.ai/api/mcp \
--header "Authorization: Bearer <your key>" \
--header "x-aeqi-company: <your company id>"
That's it. Ask your AI "what is on my AEQI team's plate?" to check it works.
Other MCP apps take the same three things: the address https://app.aeqi.ai/api/mcp, your key as a bearer token, and your company id.
What your AI can reach
Once connected, your AI can work with:
| Area | What it can do |
|---|---|
| Memory | Search, store and link what your company knows. |
| Tasks | Create, read, update and close tasks. |
| Agents | See your team and hand work to an agent. |
| Approvals | See what is waiting in Needs you. |
| Files and pages | Read and write your company's documents. |
| Apps | Use the apps your company has connected. |
Anything that leaves your company still waits for a person's OK in Needs you, however it was started.
Keep keys safe
A key acts for you inside one company. Store it like a password, never put it in code you share, and delete it from Access › API keys when you stop using it.