Guapu
io.guapuPublished by guapu.ioOfficial publisherv1.0.0Updated Oct 24, 2026
CRM AI-native para PYMEs de LATAM: contactos, ventas, cotizaciones, WhatsApp y métricas vía MCP.
Overview
Guapu is a remote MCP endpoint for a Latin American SMB CRM, exposing contacts, sales, quotes, WhatsApp and metrics to an assistant.
- What you can do
- Guapu is an AI-native CRM aimed at small and medium businesses in Latin America, reached as a remote MCP endpoint at guapu.io. According to its registry description it covers contacts, sales, quotations, WhatsApp and metrics, so an assistant could work with customer records, sales activity and quoting data through the connection. No individual tools are listed in the supplied material, so the exact operations available are not documented here.
- When to use it
- Consider it if you run a small or medium business in Latin America and already use Guapu as your CRM, and you want an assistant to reach that customer, sales and quoting data. It is less relevant if you do not use Guapu or need a CRM that is not tied to that provider.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the provider's endpoint at guapu.io. The manifest declares no authentication, no environment variables and no headers, and no packages, so nothing needs to be installed locally; a Guapu account is presumably needed to have data to work with.
Installation
In SourceWeft
- Open Guapu in the dashboard and add it to a workspace.
- 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/io.guapu%2Fguapu/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"guapu": {
"type": "http",
"url": "https://guapu.io/api/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
28% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.