Install in Claude.ai
The fastest path. Claude.ai handles the OAuth handshake automatically; you just paste the URL and authorize in the browser tab that opens.
- 1Open Settings → Connectors → Add custom connector
- 2Paste the Quallaa URL
https://www.quallaa.com/api/mcp
- 3Click Connect
A browser tab opens. Sign in to Quallaa (or sign up — it takes a minute), pick which deployment to authorize, and click Authorize.
- 4Quallaa shows up in your tools
Try `talk_to_quallaa` for a freeform conversation, or any of the panels Quallaa exposes (instructions, conversations, escalations, etc.).
Other MCP clients
All modern MCP-compatible clients work. Server URL is the same; each client has its own settings location.
Settings → Features → MCP → Add new MCP server. Type: HTTP.
Settings (gear) → MCP Servers → Add remote server.
Settings → Cascade → MCP servers → Edit config.
Treat as a remote Streamable HTTP server. OAuth handshake auto-runs.
What Quallaa exposes
One open-ended conversation tool plus the full panel surface Quallaa uses itself. Your MCP client enumerates the complete list after it connects.
Talk to Quallaa
talk_to_quallaa— Natural-language conversation. When you're not sure which panel to call, start here.
Read your deployment
show_conversations_panel— Recent customer threadsshow_escalations_panel— Open items waiting for owner actionshow_instructions_panel— Policies, tone, guardrailsshow_channels_panel— Numbers, web chat, email, voiceshow_oauth_sessions_panel— Active MCP connectors
Full tool surface (writes + standalone act tools)
show_instructions_panel__save— edit policies, tone, guardrailsshow_tools_panel__save— toggle capabilities on or offshow_escalations_panel__save— resolve an open escalationrequest_capability_authorization— request owner acknowledgement before turning on a capability that shifts the risk profileschedule_followup— queue a future follow-up the AI composes at fire timeprovision_number,enable_capability,disable_capability— capability lifecycle
The full surface grows as new capabilities land. Your MCP client's tool list is always the source of truth.
Technical detail
For developers verifying the spec or wiring Quallaa into a custom client.
- Server URL
https://www.quallaa.com/api/mcp- Transport
- Streamable HTTP (MCP 2025-06-18 spec)
- Auth
- OAuth 2.1 with PKCE (RFC 7636) and Dynamic Client Registration (RFC 7591)
- Discovery
- AS metadata at /.well-known/oauth-authorization-server
Trouble connecting?
If the OAuth flow doesn't open or fails partway, check that you can reach /.well-known/oauth-protected-resource (this should return JSON, not 404). If a tool call returns an error after connecting, paste the error into /quallaa and Quallaa will help you sort it out.