Connect Pally to Busabase
Pally is a free personal AI assistant you text on iMessage/RCS, WhatsApp, Telegram (SMS fallback); it connects to your apps and, per its changelog, to any MCP server you tell it about in chat.
Busabase MCP server
https://busabase.com/api/mcp

Set it up
Hosted chat has no shell and no file system, so a connector is the way in.
Add the server
Point your chat client at the Busabase MCP endpoint.
Sign in
Complete OAuth in the browser — no client id or secret to create.
Pick the smallest permission
changeRequest lets the agent propose but never merge.
Verify
Ask the agent to call auth_verify before it does any work.
Step by step
This host has no shell, so a connector is the only way in.
At a glance
- Vendor
- Pally Technologies, Inc.
- How it connects
- MCP + OAuth
- Transport
- Unknown
- Authentication
- Unknown
- Text your Pally (iMessage, WhatsApp or Telegram).
- Tell it to connect an MCP server and give it the URL
https://busabase.com/api/mcp. Pally's changelog: "You can now plug your own tools into Pally: tell it about any MCP server in chat." - Complete the Busabase sign-in (OAuth with dynamic client registration) that Pally asks you for; Pally's changelog says bring-your-own MCP servers connect "including OAuth and tool loading".
- Ask Pally to call
auth_verifyon Busabase.
Pally shows a heads-up about credentials before it connects a server you run yourself. If OAuth is not offered, create an API key in Busabase Settings → API Keys (smallest permission, finite expiry); Pally's docs do not say whether a custom Authorization header is accepted, so try OAuth first.
Known gotchas
No dedicated 'add a custom MCP server' documentation page: the path comes from the vendor's changelog and homepage ('Any MCP server or API with an open interface can be connected'). Transport, default OAuth scopes and Authorization-header support are not documented. pally.com/mcp is the opposite direction (Pally as an MCP server). Free for everyone, no waitlist; Cloud Mac is a separate paid add-on whose capabilities (shell?) the vendor does not describe, so the Skill path is not offered.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Mobile apps | Terminal agents | AI editors |
| Recommended path | MCP connector | Agent Skill | Agent Skill |
| How it connects | MCP + OAuth | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Unknown | Streamable HTTP | Streamable HTTP |
| Authentication | Unknown | OAuth (dynamic registration) | OAuth (dynamic registration) |
Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.
Let your agent do the setup
One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.
Browse every agentBusabase MCP server
https://busabase.com/api/mcp