VestLaunch CRM MCP Server
Moahashem/vestlaunch-mcp
Wrapper MCP auto-atualizado para o CRM VestLaunch com multi-agente
Ver no GitHubServidor MCP que expõe a API REST do CRM VestLaunch (Flat Fee Landlord) como ferramentas para agentes Claude e compatíveis. Manifesto-driven: novos endpoints no CRM emergem automaticamente como ferramentas MCP, sem alterações de código. Cada agente tem sua própria chave API, escopo e auditoria independente.
Instalação
npx convez-ai Moahashem/vestlaunch-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Integrar o CRM VestLaunch com Claude Desktop, Code ou ClawBot
- Automatizar operações de pipeline, contatos e oportunidades via agentes IA
- Auditoria descentralizada: cada agente tem seu próprio rastreamento de API
Veredito

Solução bem arquitetada de integração CRM para multi-agente, com design inteligente de manifesto dinâmico. Requer conhecimento técnico de MCP e clareza nas escopos de API, mas elimina manutenção de código quando o CRM evolui.
README
A tradução para o português deste README ainda está na fila.
vestlaunch-mcp
Model Context Protocol server for the VestLaunch CRM (Flat Fee Landlord). Manifest-driven and multi-agent — any number of Claude sessions, Claude Code instances, or other MCP-compatible agents can connect with their own per-agent API key.
The CRM (moahashem/ffl-crm) already exposes a 58-endpoint REST surface at /api/v1/* plus a machine-readable tool manifest at /api/v1/me. This MCP server is a thin wrapper that:
- Fetches the manifest at startup
- Registers each capability as an MCP tool (prefixed
vestlaunch_) - Routes tool calls back to the CRM with the agent's API key as
Authorization: Bearer ... - Logs every call to the CRM's
ApiLogtable, attributed to the calling agent
New endpoints in the CRM surface as new MCP tools automatically — no code changes here.
Why a separate repo (the multi-agent story)
Each agent that connects to the CRM has its own ApiKey row with its own scopes, rate-limit, and audit trail. Setting up the MCP as a standalone npm package means:
- Any agent on any machine can
npx vestlaunch-mcpafter exporting two env vars - Each agent sees only the tools its scopes allow (a read-only key registers fewer tools than a read+write key)
- The CRM's
ApiLogshows exactly which agent did what, automatically - One repo, one bug-fix point, ships to every agent simultaneously
Quick start (per agent)
1. Generate an API key in the CRM
In crm.vestlaunch.com, go to Settings → API Keys and create a new key:
- Name: identify the agent (e.g.
claude-cowork-lando,claude-code-mac,clawbot-vps) - Scopes: start with read-only —
contacts:read,opportunities:read,tasks:read,pipelines:read,campaigns:read,workflows:read,bookings:read,activities:read,*for/me - Rate limit: match the agent's expected call volume
Copy the key once. It won't be shown again.
2. Configure your agent
Claude Desktop / Cowork
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"vestlaunch": {
"command": "npx",
"args": ["-y", "vestlaunch-mcp"],
"env": {
"VESTLAUNCH_BASE_URL": "https://crm.vestlaunch.com",
"VESTLAUNCH_API_KEY": "ffl_live_..."
}
}
}
}
Claude Code
claude mcp add vestlaunch -- env VESTLAUNCH_BASE_URL=https://crm.vestlaunch.com VESTLAUNCH_API_KEY=ffl_live_... npx -y vestlaunch-mcp
ClawBot or any other MCP client
Spawn npx -y vestlaunch-mcp with VESTLAUNCH_BASE_URL and VESTLAUNCH_API_KEY in the environment. Stdio in, stdio out.
3. Try it
In your agent, ask:
"Use vestlaunch to summarize my pipeline by stage and source over the last 30 days."
The agent will call vestlaunch_list_opportunities, vestlaunch_get_pipelines, and any other tools it needs.
Configuration
| Env var | Required | Default | Purpose |
|---|---|---|---|
VESTLAUNCH_BASE_URL | ✅ | — | CRM API base URL, no trailing slash. |
VESTLAUNCH_API_KEY | ✅ | — | Per-agent API key from the CRM. |
VESTLAUNCH_ENABLE_WRITES | ❌ | false | Set to true to register write tools (POST/PATCH/DELETE). Tools are still gated by the key's scopes — both must allow the write. |
VESTLAUNCH_LOG_LEVEL | ❌ | info | silent | error | warn | info | debug. Goes to stderr. |
VESTLAUNCH_TIMEOUT_MS | ❌ | 30000 | Per-request timeout. |
Available tools
Tools are discovered at runtime from the CRM's /api/v1/me manifest. As of CRM v1, the read-only surface includes:
vestlaunch_list_contacts,vestlaunch_get_contactvestlaunch_list_opportunities,vestlaunch_get_opportunityvestlaunch_list_tasks,vestlaunch_get_taskvestlaunch_list_companies,vestlaunch_get_companyvestlaunch_list_properties,vestlaunch_get_propertyvestlaunch_searchvestlaunch_get_activitiesvestlaunch_get_pipelinesvestlaunch_list_tags,vestlaunch_get_custom_fieldsvestlaunch_list_campaigns,vestlaunch_get_campaignvestlaunch_list_workflows,vestlaunch_get_workflowvestlaunch_list_bookingsvestlaunch_get_mevestlaunch_get_agent_notes,vestlaunch_recall_memory,vestlaunch_query_knowledge
Enabling writes (VESTLAUNCH_ENABLE_WRITES=true) plus the appropriate scopes adds create/update/delete variants, plus vestlaunch_send_email, vestlaunch_send_sms, vestlaunch_log_call, vestlaunch_enroll_in_campaign, vestlaunch_trigger_workflow, vestlaunch_store_memory, vestlaunch_store_knowledge, and the rest of the write surface.
Tool shape
Every tool follows the same convention:
- Path parameters (
:id,:stepId, …) → required string args - GET tools → optional
query: { ... }object (passed as?key=value) - Non-GET tools → optional
body: { ... }object (sent as JSON)
Returned content is the raw CRM response JSON: { success: true, data: ..., total?, limit?, offset? }.
Development
npm install
npm run typecheck
npm run build
# Run locally against the CRM
VESTLAUNCH_BASE_URL=https://crm.vestlaunch.com \
VESTLAUNCH_API_KEY=ffl_live_... \
npm run dev
License
MIT — see LICENSE.