Client Setup
Each MCP client has its own config format, but they all point to the same endpoint and use the Api-Key header:
https://api.verbeux.com.br/mcpReplace your-api-key in the examples below with your actual key (see Authentication to generate one).
Claude Desktop
Edit the configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
json
{
"mcpServers": {
"verboo": {
"type": "http",
"url": "https://api.verbeux.com.br/mcp",
"headers": {
"Api-Key": "your-api-key"
}
}
}
}Restart Claude Desktop after saving.
Claude Code
bash
claude mcp add --transport http verboo https://api.verbeux.com.br/mcp --header "Api-Key: your-api-key"Verify the connection:
bash
claude mcp listGemini CLI
Edit ~/.gemini/settings.json:
json
{
"mcpServers": {
"verboo": {
"httpUrl": "https://api.verbeux.com.br/mcp",
"headers": {
"Api-Key": "your-api-key"
}
}
}
}Antigravity
In Settings → MCP Servers → Add Server, configure:
| Field | Value |
|---|---|
| Transport | HTTP |
| URL | https://api.verbeux.com.br/mcp |
| Header name | Api-Key |
| Header value | your API Key |
Verifying the connection
After configuring, ask your client something simple like "list my assistants". If the connection is good, it will call list_assistants and return the results.
If something fails, double-check:
- The
Api-Keyheader is exact (no spaces, same capitalization) - The URL is exactly
https://api.verbeux.com.br/mcp(no trailing slash) - Your API Key has permission for the company you're trying to manage