MCP troubleshooting
Fix common MCP connection issues.
Quick fixes for the problems people hit most often when they connect an AI client to Aloware over MCP or start using it.
For each one you'll find the symptom, the cause, and how to fix it or confirm it's working as designed. Check here first for setup trouble, activity you didn't expect, or questions about how MCP actions are tracked and charged.
The AI client won't connect
Go through the checks in this table from top to bottom. Nearly every failed connection comes down to one of them.
The AI sent an SMS or placed a call you didn't mean to
Why it happens: the AI assistant starts MCP operations from the user's prompt. What it does is driven by the instructions it's given.
What to do: treat every MCP operation as live. It uses credits exactly like the same action done by hand, and there's no dry-run mode. Check your prompt before you ask for anything that touches several contacts at once.
Rate limits
MCP has no limits of its own. Its operations share the rate limiting of the Form Capture API.
Seeing what the AI did
Each MCP communication is logged on the contact timeline as Creator Type: MCP. Filter the activity log on it to list every action that came from MCP.
Supported CRM IDs
With the contact tools you can find contacts, and enroll or disenroll them, using their contact IDs from HubSpot, Zoho, Guesty or Pipedrive.
Our support team can help you set this up.