Connect ChatGPT or Claude to Chatbotta

Add Chatbotta’s MCP server to your own ChatGPT or Claude, sign in to authorize it, and ask your AI to help set up a new project: turn your business details into knowledge, adjust the bot persona, test the bot as a customer, and see which setup steps are left.

Beta

This feature is in beta. The connection steps and the available tools may change.

MCP server URL

Add this URL in ChatGPT, Claude or any AI app that supports remote MCP servers:

https://api.chatbotta.com/mcp

Tip

After signing in to Chatbotta, open the “Account” window and choose “Connect an AI assistant” to see the steps and copy this URL. The connection uses OAuth, so you don’t need an API key.

How to connect

Claude

1. Install the Chatbotta plugin

   Open Claude on the web or desktop, go to Customize → Plugins in the sidebar, choose Add marketplace, enter Chatbotta/agent-plugins and install Chatbotta from the list.

2. Sign in and authorize

   Claude opens Chatbotta’s authorization page. Sign in with your Chatbotta account, review the permissions and choose “Allow”.

3. Start using it

   Start a new conversation and ask Claude to use Chatbotta.

Note

The plugin needs a paid Claude plan that supports Plugins. If the connector doesn’t appear by itself, add the MCP URL above in Customize → Connectors. See Claude’s help article.

Claude Code

Run this in a terminal, then follow the prompts to sign in:

claude mcp add --transport http chatbotta https://api.chatbotta.com/mcp

ChatGPT

1. Turn on Developer mode

   Turn on Developer mode under Security and login in ChatGPT’s settings. If you don’t see it, check your ChatGPT plan and account permissions.

2. Add the connection

   Go to Plugins and add a developer-mode app with the MCP URL above, choosing OAuth for authentication.

3. Sign in and authorize

   Sign in on the Chatbotta authorization page that opens, review the permissions and choose “Allow”. Then pick Chatbotta under Developer mode in a new conversation.

Note

See ChatGPT’s guide.

Codex

1. Add the Chatbotta plugin marketplace

   Run this in a terminal:

   codex plugin marketplace add Chatbotta/agent-plugins

2. Install the plugin

   Restart Codex, choose the Chatbotta marketplace in the Plugins Directory and install it.

3. Sign in and authorize

   Follow the prompts to sign in to your Chatbotta account and choose “Allow” on the authorization page.

No Chatbotta account yet?

Start connecting from your AI app anyway. On the authorization page, sign up, verify your email and create your first project; you’ll then return to the authorization page to finish connecting.

What the authorization page shows

• The app’s name and origin: apps that can prove their identity with their own domain show a “Verified by (domain)” badge. Self-registered apps show a warning and the site your access will go to (a program on your own computer shows as localhost). Only start connecting from AI apps you trust.
• The account you’re authorizing with: choose “Switch account” if it isn’t the right one.
• It will be able to: read access is “See your projects, knowledge, bot persona and setup progress”; read and write is “Add and edit knowledge and the bot persona, and ask your bot questions in project testing”.
• Projects it can access: every project you belong to now or join later, with the role you have in each.

Note

For security, the authorization page can’t be embedded in other pages. If you’re asked to open it directly in a browser tab, do that.

What you can ask the AI to do

The first version focuses on setting up new projects. Just ask in plain words, for example “Read the price list on our website and import it into Chatbotta as knowledge”, “Make the bot persona friendlier”, or “Ask a few common questions as a customer and show me how the bot answers”. The AI uses these tools:

Look things up (read access is enough)

• list_workspaces: lists the projects you can access and your role in each
• get_setup_status: shows setup progress: the getting-started checklist, the number of knowledge entries (including the samples a new project starts with), whether the bot persona is set, AI auto-reply, and whether LINE, Facebook, Instagram and website chat channels are connected, with links to the matching pages in the app
• list_knowledge: lists the project’s active knowledge
• search_knowledge: runs the same semantic search the bot uses when a customer asks something, to see which knowledge a question finds
• get_custom_prompt: reads the project’s bot persona

Make changes (needs read and write access)

• review_knowledge_import: compares new knowledge (up to 10 entries at a time) with existing knowledge to find duplicates and conflicts, using the same review as importing knowledge in the app
• apply_knowledge_import: saves reviewed knowledge, which customers get right away, using the recommended action for anything you didn’t decide; replaced entries move to the trash and can be restored in the app
• archive_knowledge: moves knowledge to the trash (up to 10 entries at a time), such as the samples a new project starts with
• update_custom_prompt: rewrites the bot persona; the previous text stays in the version history for 30 days
• preview_bot_reply: asks the bot a question as a customer; the reply uses the same AI, knowledge, bot persona and tools as real chats, plus flow changes that aren’t published yet
• deploy_bot: publishes the current draft flow, adds a version to the version history and syncs the channels’ menus (needs permission to publish in the project)

Tip

Bot persona and knowledge changes apply from the next reply, for customers too; only flows need publishing (ask the AI to publish with deploy_bot, or publish in the app). Test questions run in your own project test chat, are never billed, and you can follow them in the app.

Security and limits

• No access to customer conversations: there are deliberately no tools that read or answer customer chats. Customer messages may carry instructions aimed at AI and contain personal data, so they aren’t handed to third-party AI.
• Never more than you can do: every call checks your role in the project again. If you can’t do something in a project, neither can the AI.
• Ended plans are read-only: projects whose plan has ended can be viewed but not changed.
• AI budget: reviewing knowledge and testing the bot use AI and share the project’s daily AI budget with Copilot; it resets at midnight Taiwan time. Each connection also has a daily limit on operations.
• Channels: LINE, Facebook, Instagram and website chat are still connected under “Channels” in the Chatbotta app; the AI gives you a link to the right page.

See and revoke connections

In Chatbotta, open the “Account” window and choose “Connect an AI assistant”. “Authorized AI assistants” lists every connected AI app.

Choose “Revoke” and that app immediately loses access to your Chatbotta projects; you can reconnect from the AI app later. Your projects, knowledge and conversations are not affected.

FAQ

How is this different from external tools in “Apps”?

They work in opposite directions. This page lets your own ChatGPT or Claude connect to Chatbotta to help you set things up; external tools let your Chatbotta bot call your systems while chatting with customers (to look up orders or stock, for example).

The authorization page says the request has expired or was already used

Go back to your AI app and connect again. An authorization request lasts 60 minutes, enough time to sign up and create a project.

Who gets my project data?

Project content the AI reads through the tools (knowledge, bot persona and so on) is sent to the AI service you use and handled under your account and settings there. To stop sharing, revoke the app under “Authorized AI assistants”.

For developers

• MCP endpoint: https://api.chatbotta.com/mcp (Streamable HTTP, stateless)
• Authorization server metadata (RFC 8414): https://api.chatbotta.com/.well-known/oauth-authorization-server
• Protected resource metadata (RFC 9728): https://api.chatbotta.com/.well-known/oauth-protected-resource/mcp
• Scopes: chatbotta.read, chatbotta.write (write includes read; both are requested when none is given)

Authorization flow:

• Client registration: Client ID Metadata Documents are preferred (client_id is an https URL); Dynamic Client Registration (/oauth/register) is also supported.
• PKCE (S256) is required, and the resource parameter must be the MCP endpoint URL (RFC 8707); authorization responses include the iss parameter (RFC 9207).
• Loopback redirect URLs may use any port.
• Access tokens last 1 hour; refresh tokens last 90 days and rotate on every use.
• Token revocation: https://api.chatbotta.com/oauth/revoke.

Related

Knowledge Let AI answer customers from your knowledge

Copilot Build flows and tidy knowledge by chatting inside Chatbotta

Apps Let the bot look things up in your systems with external tools