DocsAI assistants and API
Use Adea from your AI assistant
Connect Claude, ChatGPT, Grok or Cursor to Adea, with exactly the access you have, and ask about your business from inside the assistant.
On this page
Claude, ChatGPT, Grok and Cursor can use Adea as a tool. You ask your assistant about your business, and it asks Adea, with the same access you have. This works over MCP, the standard way an AI assistant uses outside tools.
The quick way: give this to your assistant
Paste this to your assistant, and it does the steps with you:
Set up Adea for me. Read https://adea.app/assistant.md and follow its steps. If I don't have an account yet, help me create one first.
If you have no account yet, it helps you create one first. Then it asks you for your company’s address, adds it, and sends you to Adea to sign in and choose Allow. If you would rather do it yourself, the steps for each assistant are below.
Your address
Every company has its own address for assistants:
https://your-company.adea.app/mcp
Replace your-company with the address you sign in to. You can also find it in Adea, under Settings, then AI assistants.
Claude
- Open Settings, then Connectors, and add a custom connector.
- Name it Adea and paste your address.
- Sign in to Adea when Claude asks, read what the connection may do, and choose Allow.
In Claude Code, run this instead, and sign in when it asks:
claude mcp add --transport http adea https://your-company.adea.app/mcp
ChatGPT
- Open Settings and find the connectors, which are called apps in some versions.
- Turn on developer mode under Advanced, then create a connector with your address and OAuth sign-in.
- Sign in to Adea when ChatGPT asks, and choose Allow.
Grok
- Open Settings and find the connectors.
- Add a custom connector and paste your address.
- Sign in to Adea when Grok asks, read what the connection may do, and choose Allow.
Cursor
- Open the MCP settings, or edit the file
mcp.json. - Add Adea with your address:
{
"mcpServers": {
"adea": { "url": "https://your-company.adea.app/mcp" }
}
}
- Choose Login when Cursor shows it, sign in to Adea and choose Allow.
For Cursor and other tools, the sign-in screen says Adea hasn’t verified the app by name. Check that the name and address are the ones you just set up, and choose Allow.
Note. The menus in each assistant change from time to time. If a name above doesn’t match, look for “connectors”, “apps” or “MCP servers” in its settings.
What happens when you connect
- The assistant opens a sign-in page at Adea.
- You sign in as yourself. Adea shows what the connection is, and the role it gets, which can be at most your own.
- You choose Allow. The assistant is now connected to your company, and to that company only.
What an assistant can and can’t do
- It sees what you see, and no more. An assistant can do at most what both its own role and your role allow.
- Every call is logged in your name. You can see what an assistant did.
- It can’t confirm for you. When an action needs a person’s confirmation, the assistant gets a link for you to open. Only your own click confirms.
- Reading data comes first. Once an assistant has read your data in a conversation, any change in that conversation waits for your click.
- Guardian watches. The same checks apply to an assistant’s questions as to yours. See Guardian.
- Each answer starts with a sentence to read aloud, for when you talk to your assistant hands-free.
Demo companies can’t be connected to an assistant.
Disconnect
Open Settings, then AI assistants, and disconnect the assistant. It stops working at once and its access is deleted. When a person leaves the company, every assistant they connected stops working too.
Still stuck? Write to hello@adea.app. A person answers.