Use Chatasist from your AI assistant
Connect Chatasist to Claude, ChatGPT, Cursor or any MCP-compatible assistant, sign in with your Chatasist account, and work in your inbox, tickets and settings by asking.
Chatasist has its own MCP server. Add it to an AI assistant that supports the Model Context Protocol — Claude, ChatGPT, Cursor, VS Code, Claude Code and others — and the assistant can work in Chatasist for you: summarize today's conversations, reply to a customer, open or move a ticket, change a setting, or explain how a feature works.
This is the opposite direction of MCP servers, which let Chatasist's AI agent call your tools while it talks to customers. Here, your assistant uses Chatasist.
Server address#
https://api.chatasist.com/mcp
You don't need an API key. When you connect, a Chatasist sign-in window opens and you sign in with your usual Chatasist email and password (and your two-factor code, if you use one).
Connect your assistant#
In Claude, open Settings → Connectors → Add custom connector, name it Chatasist, paste the server address, and click Connect. Sign in when the Chatasist window opens.
Sign in
Enter your Chatasist email and password. If you're already signed in to app.chatasist.com in the same browser, this step is skipped.
Choose a workspace
If you belong to more than one workspace, pick the one the assistant should work in. You can switch later by asking — for example, "switch to my Acme workspace".
Allow access
Check that the app name and the return address are the assistant you're connecting, then click Allow access.
Signed up with Google and never set a password? Sign in to app.chatasist.com with Google in the same browser first and then connect — or set a password with Forgot password on the sign-in page.
What your assistant can do#
The assistant acts as you: it sees what you can see and can only change what your role allows. A read-only member's assistant can read but not change anything; billing and team changes still need an administrator.
List and search conversations, read a conversation, reply to the customer or leave an internal note, assign it, and mark it in progress or resolved.
Search tickets, open a board, create tickets, move them between stages, and comment — optionally emailing the customer.
Look up customers and their history, and check what your AI agent knows about a topic in your knowledge bases.
Most things you can do in the app: AI agent settings, playbooks, labels, macros, work schedules, channels, integrations, team members and more.
It can also read this help center, so you can ask things like "how do I connect WhatsApp?" or "what does the unhappy view show?" and get step-by-step answers with a link to the right page.
A few things stay in the app on purpose: changing your password, two-factor or email, deleting your account or workspace, creating API keys, payments and plan changes, downloading exports, and connecting channels that need a Facebook/Instagram pop-up.
Good things to ask#
- "Summarize the unread conversations from today and suggest replies."
- "Reply to Jane's chat that her refund was issued — show me the text first."
- "Open a ticket on the Support board for order 1042 and assign it to me."
- "Show me this week's resolved conversations with unhappy customers."
- "Add a label called VIP in dark blue."
- "How do I set up holidays so the AI agent tells customers we're closed?"
Replies and ticket comments sent through your assistant reach real customers, just like sending them from the app. Good assistants confirm before sending — review the text before you agree.
Disconnect#
Remove the Chatasist connector in your assistant's settings.
Troubleshooting#
- "You belong to several Chatasist workspaces" — ask the assistant to list your workspaces and switch to one.
- "You do not have permission to perform this action" — your role doesn't allow that change; ask a workspace administrator.
- The sign-in window doesn't open — make sure your assistant supports remote MCP servers with OAuth sign-in, and that pop-ups aren't blocked.