WhatsApp Agent

Created By
aasherkamal216a year ago
A WhatsApp agent that uses WhatsApp MCP server to send messages and perform other actions.
Overview

What is WhatsApp Agent?

WhatsApp Agent is a tool that interacts with WhatsApp using the WhatsApp MCP server to send messages and perform various actions on behalf of the user.

How to use WhatsApp Agent?

To use WhatsApp Agent, set up the WhatsApp MCP server, clone the repository, install dependencies, and run the Chainlit app to interact with WhatsApp.

Key features of WhatsApp Agent?

  • Search for contacts by name or phone number
  • Retrieve messages with optional filters
  • List available chats with metadata
  • Send messages, files, and audio messages
  • Download media from WhatsApp messages

Use cases of WhatsApp Agent?

  1. Sending messages to contacts or groups.
  2. Retrieving and listing recent chats.
  3. Downloading media files from conversations.
  4. Searching for specific contacts or messages.

FAQ from WhatsApp Agent?

  • What are the prerequisites to use WhatsApp Agent?

You need Python 3.10+, WhatsApp MCP server, and an OpenAI API key.

  • Is there a graphical interface for WhatsApp Agent?

Yes, you can run the Chainlit app to interact with WhatsApp through a web interface.

  • Can I send files other than text messages?

Yes, you can send images, videos, audio files, and documents.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aasherkamal216
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago