Ouzap — WhatsApp for agents

br.com.ouzapPublished by ouzap.com.brOfficial publisherv1.0.0Updated Oct 29, 2026

Read, reply to and schedule WhatsApp messages from your Ouzap number. Made in Brazil.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Ouzap connects an assistant to a WhatsApp number so it can read, reply to and schedule messages.

What you can do
  • Read incoming WhatsApp messages from the Ouzap number
  • Reply to conversations on the user's behalf
  • Schedule messages to be sent later
  • Operates as a hosted remote service, so no local package is installed
When to use it
Useful when an assistant should handle WhatsApp conversations tied to an Ouzap number, such as drafting replies or queuing messages for later, without a local bridge.
Requirements
A remote MCP endpoint at the provider's domain over streamable HTTP, plus OAuth sign-in to an Ouzap account and an active WhatsApp number on that service. No environment variables or headers are declared.
Before you install
The assistant can send and schedule messages from a real WhatsApp number, so replies reach real contacts and cannot be unsent. Access is granted through OAuth to the Ouzap account, and message content passes through the provider's hosted service.

Installation

In SourceWeft

  1. Open Ouzap — WhatsApp for agents in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/br.com.ouzap%2Fwhatsapp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ouzap-whatsapp-for-agents": {
      "type": "http",
      "url": "https://ouzap.com.br/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.