Z API MCP server
MCP server for Z-API — WhatsApp messaging, contacts, media
271 stars
Reviews
Write oneNobody has reviewed Z API yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Z API tools (27, 12 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
add_contactsAdd one or more contacts to the WhatsApp address book. Accepts an array of contacts.
add_group_participantAdd a participant to a WhatsApp group
add_labelAssign a label/tag to a chat
check_numberCheck if a phone number has WhatsApp
create_groupwrite actionCreate a WhatsApp group
delete_messagewrite actionDelete a message
get_contact_metadataGet metadata (name, WhatsApp display name, profile picture, status) for a single contact
get_contactsGet all WhatsApp contacts
get_group_metadataGet group metadata and participants
get_labelsList all available labels/tags
get_messagesGet messages for a phone number
get_profile_pictureGet profile picture URL for a phone number
get_statusGet WhatsApp instance connection status
list_chatsList all WhatsApp chats with pagination
list_groupsList all WhatsApp groups with pagination
mark_chat_as_readMark an entire chat as read or unread
read_messageMark messages as read
remove_group_participantwrite actionRemove a participant from a WhatsApp group
send_audiowrite actionSend an audio message via WhatsApp
send_button_actionswrite actionSend interactive action buttons (CALL, URL, REPLY). Do not mix REPLY with CALL/URL in the same message.
send_button_listwrite actionSend a button list message via WhatsApp
send_contactwrite actionSend a contact card via WhatsApp
send_documentwrite actionSend a document via WhatsApp
send_imagewrite actionSend an image message via WhatsApp
send_locationwrite actionSend a location message via WhatsApp
send_option_listwrite actionSend an interactive option list (WhatsApp native list). Does NOT work in groups.
send_textwrite actionSend a text message via WhatsApp
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 29 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Z API compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 27
- the typical server has 7
- Tools that change things
- 44%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 271
- more than 95% of 28,688 servers
What its tools let an agent do: 11 read · 4 create · 1 change · 2 delete · 9 send or post
Install Z API in Claude Code, Cursor or VS Code
Runs npx -y @codespar/mcp-z-api on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-z-api -- npx -y @codespar/mcp-z-api
What the publisher says
From the Z API repository's README, as published. We do not edit it. Read it on GitHub
MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute
The Problem
AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).
Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.
MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.
The Solution
Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.
🛒 Customer places order
→ 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
→ 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
→ 📦 Agent generates shipping label (Melhor Envio / Skydropx)
→ 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
→ 📊 Agent records in ERP (Omie / Bling / Tiny)
→ 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)Six systems. Zero human intervention. One agent.
Agentic Payment Protocols
Four servers for the emerging agentic payment stack:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Z API: common questions
- Is Z API MCP server safe?
- Mostly: it is graded B (82/100). Read the Z API safety report
- How do I install Z API?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Z API need an API key?
- Yes. The registry entry asks for
ZAPI_TOKEN. - Is Z API maintained?
- The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.
- How does Z API compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 27 (the typical server has 7); tools that change things 44% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.