Connect an AI assistant like Claude or ChatGPT
Updated Nov 19, 2026
Aigento's connector lets an AI assistant such as Claude or ChatGPT work in
your workspace from its own chat. Once connected, you can ask it to look up
tickets, search your knowledge base, check how your team is doing, draft
replies and macros for your team to review, and, if you allow it, reply to
customers and update tickets.
The assistant only ever works in the one workspace you connect it to, and
only with the access level you choose.
The server URL
https://app.aigen.to/api/mcpYou also find it, with a copy button, under Settings → Integrations → MCP
server.
Before you start
- You need to be an owner or admin of the workspace. Members cannot
connect an assistant. - Decide which access level the assistant should have (see below). You can
connect again later with a different level.
Connect from Claude
- In Claude, open Settings → Connectors and click Add custom
connector. - Paste the server URL and add it. No client ID or secret is needed.
- Claude opens Aigento in your browser. Sign in if you are not signed in
already. - On the Connect Claude? page, pick the workspace (if you have more than
one) and the access level. The page lists the tools that level allows. - Click Approve. You are sent back to Claude, and the connector is ready.
Connect from ChatGPT
- In ChatGPT, add a custom connector (app) from its settings and paste the
server URL. Depending on your ChatGPT plan, this may first need to be
allowed by your ChatGPT workspace admin. - Choose OAuth sign-in if ChatGPT asks how to authenticate.
- ChatGPT opens Aigento in your browser. Sign in, pick the workspace and the
access level, and click Approve.
Connect with a token instead
Some assistants and scripts cannot open a browser to sign in. For those:
- Go to Settings → Integrations → MCP server and, under API tokens
(MCP), click New token. - Name it, choose its access level and click Create token.
- Copy the token. It is shown once.
- In your client, use the same server URL and send the token as
Authorization: Bearerfollowed by the token.
Access levels
Each level includes everything in the levels above it.
Read — looks things up and changes nothing:
- List tickets, Get ticket, Get ticket AI activity
- Search knowledge base, Get knowledge-base article
- Search product help, Get product help article (Aigento's own help articles)
- List automations
- Get workspace settings, Get workspace stats, Get setup status
Draft — also creates things that do nothing until a person on your team
acts on them:
- Draft ticket reply: the reply waits in your review queue and is only sent
if someone on your team approves it. - Draft an automation: created switched off.
- Draft a knowledge-base article: created unpublished, so your AI agent does
not use it yet. - Edit a knowledge-base article: only an unpublished draft at this level.
- Draft a custom endpoint: created switched off and not offered to your AI
agent until an admin tests it and turns it on. - Create a macro: a saved reply your team can pick; it sends nothing by
itself. - Create an inbox view: a personal view for the person who connected the
assistant.
Full — also acts without a person in between:
- Send ticket reply: sends a reply to the ticket's own customer. It can only
reply when the customer wrote last, and it can never send to any other
address. Your workspace's undo window still applies, and in sandbox mode
nothing is delivered. - Update ticket: changes status, priority, assignee or tags. Resolving or
closing a ticket can send your satisfaction survey, if you have one turned
on. - Update chat widget settings
- Edit a knowledge-base article that is published or archived: a published
article's change reaches your AI agent's answers at once. - Publish a knowledge-base article and Unpublish a knowledge-base article:
publishing lets your AI agent use the article at once; unpublishing makes
it a draft again. - Invite team member and Resend invitation: the invitee gets an email with a
sign-in link. The owner role cannot be given this way.
Choose Read or Draft unless you want the assistant to reply to
customers on its own.
Disconnect
Go to Settings → Integrations → MCP server, find the connection in the
token list (a connection made by approving in the browser appears there too)
and click Revoke. The assistant loses access immediately, on its very
next request.
Access also ends on its own when the person who connected it leaves the
workspace or stops being an owner or admin.
Limits
- Each connection can make up to 60 tool calls per minute. Beyond that,
the assistant is told to wait a few seconds and try again. - Every call is listed in the Activity tab of the MCP server integration,
with which tool ran and whether it worked.
Things to ask
- "Which tickets came in since yesterday that are still open?"
- "Summarise ticket 1042 and draft a reply for my team to review."
- "Search our knowledge base for the returns policy and tell me if it covers
sale items." - "How did our support do this week compared with last week?"
- "Create a macro for customers asking where their order is."
- "Draft an automation that tags every ticket mentioning a refund."
Troubleshooting
I keep landing on the sign-in page. Aigento signs you in with a link sent
by email. Open that link in the same browser that opened Aigento for the
connector, then start the connection again from your assistant if it does not
continue by itself. A browser that blocks cookies for app.aigen.to will also
send you back to sign-in.
"No eligible workspace." You are not an owner or admin of any workspace
where the connector is available. Ask a workspace owner to connect it or to
change your role.
"The Aigento MCP server is not enabled for this workspace." The connector
is not available to this workspace right now. Contact support. If the
message says the workspace is scheduled for deletion, cancelling the deletion
restores access.
A tool is refused for its access level. The message names the level the
connection has and the level the tool needs. Connect again and choose the
higher level, or create a token with it.
"Unauthorized: unknown or revoked API token." The connection was revoked
or its person left the workspace. Remove the connector from your assistant
and connect again.
A tool says it failed on Aigento's side. Nothing was wrong with your
request. A lookup can simply be tried again. A change, such as a reply or a
ticket update, may have gone through anyway: check the ticket or setting in
Aigento, or ask the assistant to look it up, before trying again. If it keeps
failing, write to [email protected].
What the assistant can see
The assistant receives what the tools return, only from the workspace you
connected and only when it calls a tool. Depending on the access level, that
includes ticket subjects, statuses and customer email addresses, full ticket
conversations, what your AI agent did on a ticket, your knowledge-base
articles, automation names and triggers, chat widget settings, team size,
support statistics and your plan's usage. It never receives API keys,
tokens, passwords or payment details, or anything from another workspace.
What the assistant's provider does with that data is governed by your
agreement with them. Aigento's own handling is described in the
privacy policy.