Repository navigation
Add Ouzap (WhatsApp) to the connector catalogue - #850
Open
rehoboam-karl wants to merge 1 commit into
Open
rehoboam-karl wants to merge 1 commit into
rehoboam-karl wants to merge 1 commit into
Conversation
Ouzap runs a hosted MCP server for WhatsApp with OAuth discovery, dynamic client registration and PKCE as a public client, the same shape as Notion, so it fits the catalogue without new machinery. Sending, replying, scheduling and creating a contact are pinned as writes; contacts:write is not requested. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rehoboam-karl
requested review from
MikeRyanDev,
davidmckayv,
guidovizoso,
mxmzb and
tylerslaton
as code owners
October 27, 2026 14:16
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Ouzap to the connector catalogue. Ouzap is a Brazilian WhatsApp gateway with a hosted MCP server, so a Bot can list, read and reply to the WhatsApp conversations on a person's Ouzap number and start new ones.
Why a catalogue entry
Ouzap's MCP server only accepts OAuth. A server added by URL takes a static bearer credential, so today it cannot be connected without a code change. Ouzap has the same shape as Notion, so it needs no new machinery:
/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-serverare both published./oauth/register.token_endpoint_auth_methods_supported: ["none"], PKCES256.Choices worth a look
conversations,messages:readandmessages:write, which match Ouzap's consent screen ("read and reply to WhatsApp conversations").contacts:writeis left out, socreate_contactfails at the vendor.create_contact,reply_conversation,schedule_whatsapp_messageandsend_whatsapp_messageare pinned in the test. Every one of them reaches a real person's phone.readToolsnames the six reads (get_message_status,list_conversations,list_scheduled_messages,list_whatsapp_numbers,read_conversation,search_contacts). Anything else Ouzap advertises later classifies as a write until reviewed, as with Exa and Firecrawl, because a sending tool that slipped through as a read would message real people.revocation_endpoint.revokeUrlpoints at the token endpoint, as Notion's does, and nothing reads the field today.Tests
server/tests/plugin-catalogue.test.tsgets an Ouzap block mirroring Notion's: transport, https-pinned endpoints, scopes, and the pinned write list.bun run typecheck(server) andbiome format/biome lintare clean on the changed files.mainand on this branch, so they come from the environment and not from this change.Note
The write-tool names come from the tool listing Ouzap's server advertises today. The OAuth endpoints were read live from Ouzap's discovery documents, but the full consent flow has not yet been run end to end against this branch. A first Refresh tools after enabling is the reconciliation the Notion entry calls for.
🤖 Generated with Claude Code