Connect other AI apps
Connect WhatsAble to any app that speaks MCP: the settings it needs, how sign-in works, how to send an API key instead, and how to bridge an app that only runs local servers.
Any app that can add a remote MCP server can use WhatsAble. Its settings may call it a connector, an integration, a custom app or a tool server. On WhatsAble, you need to be an owner or an admin, on a plan that includes the API. See What you need.
The settings
| Setting | Value |
|---|---|
| Server URL | https://api.whatsable.app/mcp |
| Transport | Streamable HTTP. Some apps call it HTTP. Not SSE. |
| Authentication | OAuth. The app registers itself, so there is no client ID or secret to enter. |
| Or: a header | Authorization: Bearer nfy_live_..., with an API key |
How sign-in works
When the app first connects, WhatsAble answers that it needs a sign-in, and tells the app where to find it. A standard MCP app takes it from there: it opens WhatsAble in your browser, you sign in, choose the organization, the access and the numbers, and Approve. Access and connections shows each page.
The app then holds a token that lasts one hour and renews itself. If you don't use the app for 30 days, it asks you to sign in again.
For developers, the details:
- Protected resource metadata:
https://api.whatsable.app/.well-known/oauth-protected-resource/mcp - Authorization server metadata:
https://api.whatsable.app/.well-known/oauth-authorization-server - Dynamic Client Registration (RFC 7591) is open. Client ID Metadata Documents are not supported yet.
- The authorization code flow with PKCE (
S256), and refresh tokens. There is no client credentials grant: every connection belongs to a person who approved it.
Use an API key
When an app cannot sign in with OAuth, or runs where no browser can open, send an API key instead. Create one in WhatsAble under Settings > API keys, and set the header:
Authorization: Bearer nfy_live_...The key's own access and numbers apply, and it works until you revoke it. Keep it in the app's secret storage, never in a file you share.
Apps that only run local servers
Some apps can only start a local MCP server, a command on your computer. The open-source mcp-remote package bridges them to WhatsAble. It needs Node.js. Add a server whose command is:
{
"mcpServers": {
"whatsable": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.whatsable.app/mcp"]
}
}
}mcp-remote opens the WhatsAble sign-in in your browser the first time it runs. It is not made by WhatsAble. Prefer the app's own remote server setting when it has one.
Remove it
Remove WhatsAble in the app. Then revoke the connection in WhatsAble, under Settings > API keys > Connected AI apps: removing it in the app does not. See Revoke a connection.
More in Troubleshooting.