Build your assistants
Create an assistant from a business website, check preparation and update how it responds.
“List my assistants and show which ones are ready.”
CHIRPS MCPAsk your AI to
work in Chirps.
Manage assistants, update their knowledge and review customer activity from the AI application you already use.
Add Chirps as an MCP connection. Sign in, choose your workspace, then ask for what you need in the conversation.
How the connection works
Your conversation becomes a way to get things done.
MCP stands for Model Context Protocol. It lets your AI application discover Chirps tools and use them with the access you approve.
01
You ask in your AI app
“Show me recent leads in my Chirps workspace.”
02
The app calls a Chirps tool
Chirps checks your connection and workspace permissions, then returns the requested records.
03
The result appears in your chat
Your AI app uses the returned information to answer you and help with the next step.
You approve one workspace per application. Existing owner or administrator permissions and plan limits still apply. Review changes before asking your AI app to save them.
What you can do
Put your business context to work.
Keep knowledge current
Review saved knowledge and add approved business information for your assistant to use.
“Add these opening hours to my assistant’s knowledge.”
Understand conversations
Read saved customer conversations and use your AI app to help spot recurring questions.
“Show me the recent conversations for this assistant.”
Follow up with leads
Review captured leads and update a lead’s status after your team follows up.
“List recent leads, then mark this one contacted.”
Review bookings & activity
Read bookings and workspace analytics without switching to another dashboard.
“Show my workspace’s upcoming bookings.”
Get ready to install
Get the website embed snippet and inspect an assistant’s installed connector tools.
“Give me the installation snippet for my assistant.”
Set it up in your AI app
Pick your app. Follow its connection steps.
The connection is added in the AI application’s MCP or connector settings. Your Chirps sign-in comes afterward.
MCP server URL
https://chirps.cc/api/mcpStreamable HTTP · Sign in with your Chirps account
Sign in to connect your workspace
Your AI app registers the connection automatically. Chirps asks you to sign in and choose a workspace. Live connections in the apps below are still awaiting verification.
- 1
Open your connector settings
In Claude, open Customize → Connectors, then Add custom connector. Team administrators add it through organization settings.
- 2
Enter Chirps and the server URL
Name the connector Chirps. Paste https://chirps.cc/api/mcp as the remote server URL.
- 3
Choose automatic registration
Choose sign-in authentication, then Register automatically under OAuth client. Claude registers its connection with Chirps during setup.
- 4
Sign in and start a conversation
Connect, sign in to Chirps and approve one workspace. Enable Chirps in the conversation’s Connectors menu, then ask it to list your assistants.
Your connector details
- Name
- Chirps
- Remote MCP server URL
- https://chirps.cc/api/mcp
- Authentication
- Sign in
- OAuth client
- Register automatically
Instructions follow the application’s documentation. A live Chirps connection must still be verified.
Official setup guideA few things to know
Clear access.
Clear expectations.
Chirps handles assistant management and customer activity through this connection. Payments, phone purchases and executing installed connector actions use the dashboard.
Manage connected appsWhat am I adding to my AI app?
A remote connection to Chirps’s tools. Your AI app can call those tools to read or change the workspace you approve. Chirps handles the action and sends the result back into that conversation.
Do I need to install Chirps on my computer?
Chirps hosts the MCP server. You configure the connection in your AI application. Claude Code and Cursor use their own local configuration; Claude’s remote connectors use its connector settings.
Do I need a client ID?
The standard setup uses automatic OAuth registration. Add the server URL, then follow your AI application’s Chirps sign-in flow. An existing client ID is only needed for a custom registration or an application that cannot register automatically.
Is this the Chirps chatbot inside Claude?
The AI application stays the interface you speak to. It uses Chirps tools on your behalf. Your website assistant continues serving customers through its widget and other configured channels.
Will every MCP app work?
The client needs remote Streamable HTTP and OAuth sign-in with automatic registration, or an existing registered client. The guides below describe documented configuration paths; live compatibility has to be verified for the application and version you use.
How do I stop access?
Disconnect the application from Chirps’s Connected apps page. Future requests are blocked. Completed changes and information already shared with the other provider remain subject to their normal records and privacy practices.
Bring Chirps into your next conversation.
Choose your AI app, add the server and sign in to your Chirps workspace.
Set up your connectionConnected apps may receive customer information you request. Review the app’s privacy terms and Chirps’s Privacy Policy.