Servidor MCP
Conecte um assistente de IA à sua conta com o protocolo MCP. Ele usa a sua chave de API e só oferece as ferramentas permitidas para essa chave.
Não disponível
GET/mcp
O servidor MCP não abre um canal SSE: todas as requisições vão por POST /mcp.
Permissões: contacts:read contacts:write conversations:read messages:send campaigns:read campaigns:write automations:read reports:read templates:read templates:send wallet:read bots:read
curl "https://micuenta.whatsmarketing.es/api/v1/mcp" \
-H "Authorization: Bearer $WM_API_KEY"const res = await fetch('https://micuenta.whatsmarketing.es/api/v1/mcp', {
headers: {
Authorization: `Bearer ${process.env.WM_API_KEY}`,
},
});
const data = await res.json();import os, requests
r = requests.get(
"https://micuenta.whatsmarketing.es/api/v1/mcp",
headers={"Authorization": f"Bearer {os.environ['WM_API_KEY']}"},
timeout=30,
)
r.raise_for_status()
data = r.json()<?php
$ch = curl_init('https://micuenta.whatsmarketing.es/api/v1/mcp');
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('WM_API_KEY'),
],
]);
$data = json_decode(curl_exec($ch), true);Ainda sem exemplo de resposta.
Servidor MCP
POST/mcp
Ponto de entrada do protocolo MCP (JSON-RPC 2.0 por HTTP). tools/list retorna as ferramentas que a sua chave permite. Só enviar_plantilla gasta saldo, e em dois passos: a primeira chamada retorna o custo e uma confirmação válida por 5 minutos, e a segunda, com essa confirmação, envia. Cada chave pode enviar até 100 modelos por dia pelo MCP.
Permissões: contacts:read contacts:write conversations:read messages:send campaigns:read campaigns:write automations:read reports:read templates:read templates:send wallet:read bots:read
Parâmetros
| Nome | Onde | Tipo | Valores |
|---|---|---|---|
Idempotency-Key | consulta | string | 1–255 caracteres |
curl -X POST "https://micuenta.whatsmarketing.es/api/v1/mcp" \
-H "Authorization: Bearer $WM_API_KEY"const res = await fetch('https://micuenta.whatsmarketing.es/api/v1/mcp', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.WM_API_KEY}`,
},
});
const data = await res.json();import os, requests
r = requests.post(
"https://micuenta.whatsmarketing.es/api/v1/mcp",
headers={"Authorization": f"Bearer {os.environ['WM_API_KEY']}"},
timeout=30,
)
r.raise_for_status()
data = r.json()<?php
$ch = curl_init('https://micuenta.whatsmarketing.es/api/v1/mcp');
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('WM_API_KEY'),
],
]);
$data = json_decode(curl_exec($ch), true);Ainda sem exemplo de resposta.
Não disponível
DELETE/mcp
O servidor MCP não guarda sessão, então não há nada para fechar.
Permissões: contacts:read contacts:write conversations:read messages:send campaigns:read campaigns:write automations:read reports:read templates:read templates:send wallet:read bots:read
curl -X DELETE "https://micuenta.whatsmarketing.es/api/v1/mcp" \
-H "Authorization: Bearer $WM_API_KEY"const res = await fetch('https://micuenta.whatsmarketing.es/api/v1/mcp', {
method: 'DELETE',
headers: {
Authorization: `Bearer ${process.env.WM_API_KEY}`,
},
});
const data = await res.json();import os, requests
r = requests.delete(
"https://micuenta.whatsmarketing.es/api/v1/mcp",
headers={"Authorization": f"Bearer {os.environ['WM_API_KEY']}"},
timeout=30,
)
r.raise_for_status()
data = r.json()<?php
$ch = curl_init('https://micuenta.whatsmarketing.es/api/v1/mcp');
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'DELETE',
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . getenv('WM_API_KEY'),
],
]);
$data = json_decode(curl_exec($ch), true);Ainda sem exemplo de resposta.