Sitespeakai
SiteSpeakAI enables businesses to automate customer support by creating custom-trained, embeddable GPT chatbots that provide real-time answers about products and services, reducing support tickets.
Verdict
Common use cases
- Audit smart prompts across all chatbots
- Verify which bots are live on your account
- Troubleshoot chatbot access issues from Slack
- Document prompt libraries for compliance reviews
- Check user permissions before onboarding teammates
Integration
- Vendor
- Sitespeakai
- Category
- communication
- Auth
- API_KEY
- Tools
- 3
- Composio slug
sitespeakai
Tools
- Get Authenticated User
Tool to retrieve details of the authenticated user account. use after obtaining a valid bearer token and when you need the current user's profile.
- Get Smart Prompts
Tool to retrieve smart prompts available for a chatbot. use when you need to list prompts before selecting or managing them.
- List Chatbots
Tool to list all chatbots. use when you need an overview of every chatbot linked to your account. no parameters required.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Add MCP. 2. Search for Sitespeakai and click Connect. 3. Log into your Sitespeakai account in a separate tab and go to Account Settings or API Access to generate a new API key. 4. Copy the key and paste it into the Switchy connection dialog, then click Authorize. 5. Switchy confirms the connection by fetching your user profile in the background. 6. Open any Space and type '@Sitespeakai list all chatbots' to verify the integration works. 7. If you see a list of your bots, the connection is live and you can start querying prompts or account details.
What teammates see: by default, memories from Sitespeakai are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Chatbots
@Sitespeakai list all chatbots on my account. Show me the name and ID for each one.Open in a Space →
Fetch Smart Prompts
@Sitespeakai get the smart prompts for chatbot ID [paste ID here]. List each prompt title and its purpose.Open in a Space →
Check My User Profile
@Sitespeakai retrieve my authenticated user profile. Show me my account name and email.Open in a Space →
Compare Prompt Libraries
@Sitespeakai get smart prompts for chatbot [ID A] and chatbot [ID B]. Compare the prompt titles and highlight any unique to each bot.Open in a Space →
Audit Bot Inventory
@Sitespeakai list all chatbots and for each one tell me how many smart prompts it has configured.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@sitespeakai list all chatbots in my account and show me their current status and configuration
Retrieved 4 chatbots from your Sitespeakai account: 'Support Bot' (active, 127 conversations this month), 'Sales Assistant' (active, 89 conversations), 'Onboarding Guide' (paused), and 'FAQ Helper' (active, 203 conversations). Each bot is configured with custom prompts and connected to different website domains. Support Bot and FAQ Helper are handling the highest volume.
This example shows the MCP's ability to inventory your chatbot deployment. Requires a valid API key with read access to chatbot resources. Useful for auditing which bots are live and their relative usage, though detailed analytics require separate queries.
@sitespeakai get the smart prompts configured for my Support Bot and show me which ones are most commonly triggered
Found 8 smart prompts for 'Support Bot': 'Billing Questions' (triggered 34 times this week), 'Account Setup Help' (29 times), 'Feature Requests' (12 times), 'Bug Reports' (8 times), and 4 others with lower frequency. Each prompt includes predefined response templates and escalation rules. Billing Questions and Account Setup Help are your primary user intents.
Demonstrates how the MCP surfaces chatbot conversation patterns through prompt analytics. You'll need to know your chatbot's identifier beforehand (from the list chatbots tool). Helps identify which conversation flows need refinement based on actual usage data.
@sitespeakai check my authenticated user details and tell me what access level and quota limits apply to my account
Your Sitespeakai account (email: team@example.com) is on the Professional plan with admin-level access. Current quota: 4 active chatbots (limit: 10), 419 conversations this month (limit: 5,000), API rate limit of 100 requests per minute. Account created March 2024, last login 2 hours ago. You have full permissions to create, modify, and delete chatbots.
This example shows account-level context retrieval, useful before performing bulk operations or when troubleshooting API access issues. The MCP returns your authentication status and plan limits, helping you understand what actions are available and whether you're approaching quota boundaries.
Use-case deep-dives
When Sitespeakai works for support team onboarding
A 6-person support team rotating weekend shifts needs a single source of truth for which chatbot handles which product line. The List Chatbots tool gives you a live inventory without digging through admin panels, and Get Smart Prompts shows the exact phrasing each bot uses so new hires can match customer questions to the right escalation path. This MCP is overkill if you run one chatbot or your team already has a wiki. It pays off when you have 3+ bots with overlapping domains and turnover means someone is always learning the setup. If your onboarding doc is stale more than once a quarter, pull chatbot metadata into Switchy and keep it current.
Why agencies use this for monthly client reviews
A 3-person agency managing chatbots for 8 SaaS clients needs to report prompt performance without logging into 8 separate dashboards. The Get Smart Prompts tool surfaces which prompts are live for each client, and Get Authenticated User confirms you are pulling the right account before you screenshot anything for a deck. This MCP is a time-saver if you bill hourly and context-switching costs you 10 minutes per client. It is not worth the API key setup if you only manage one or two clients or if your clients give you read-only dashboard access that is faster to click through. If you are preparing more than 4 client reviews a month, automate the pull and spend the saved time on strategy.
When this MCP helps product teams stay aligned on bot behavior
A 5-person product team shipping a new feature needs to verify that the chatbot prompts reflect the updated workflow before the release goes live. The Get Smart Prompts tool lets you compare prompt text against the spec doc in Switchy without asking the support lead to export a CSV. This MCP is useful if your release cadence is weekly or faster and your chatbot is customer-facing enough that a stale prompt creates confusion. It is not worth the overhead if your chatbot is internal-only or if you ship quarterly and can afford a manual check. If you have caught a prompt-spec mismatch in production more than once, pull prompts into your pre-launch checklist and close the gap.
Frequently asked
What does the Sitespeakai MCP do in Switchy?
It connects your Sitespeakai chatbot account to Switchy so your team can list chatbots, retrieve smart prompts, and pull authenticated user details without leaving the workspace. Useful if you're managing multiple chatbots and want to query their configuration or prompt libraries programmatically instead of logging into the Sitespeakai dashboard.
Do I need admin access to connect Sitespeakai?
You need an API key from your Sitespeakai account. Whoever generates the key will determine which chatbots and prompts Switchy can see. If your Sitespeakai account restricts API key creation to admins, then yes—otherwise any user with key-generation rights can connect it.
Can the Sitespeakai MCP create or edit chatbots?
No. The three tools are read-only: list chatbots, get smart prompts, and retrieve the authenticated user profile. If you need to create chatbots or modify prompt libraries, you still have to do that in the Sitespeakai web app or use their full API directly.
Why use this MCP instead of the Sitespeakai dashboard?
If your team already works in Switchy and you want to reference chatbot names or prompt text inside a shared conversation, the MCP saves you from tab-switching. For one-off setup tasks or bulk edits, the Sitespeakai dashboard is still faster because the MCP doesn't expose creation or update endpoints.
Who on the team should connect the Sitespeakai MCP?
Whoever owns the Sitespeakai API key. That person's key determines which chatbots and prompts the entire Switchy workspace can query. If you rotate API keys or have multiple Sitespeakai accounts, you'll need to reconnect the MCP each time the key changes.