MCP Server for Ambivo API endpoints - Natural language queries and direct entity data access
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ambivo-mcp-server-fastmcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
[](https://fastmcp.me/MCP/Details/1410/ambivo) [](https://fastmcp.me/MCP/Details/1410/ambivo) [](https://fastmcp.me/MCP/Details/1410/ambivo) [](https://fastmcp.me/MCP/Details/1410/ambivo) [](https://fastmcp.me/MCP/Details/1410/ambivo) [](https://fastmcp.me/MCP/Details/1410/ambivo) # Ambivo Claude MCP Server This Claude MCP (Model Context Protocol) server provides access to Ambivo API endpoints for natural language querying of entity data with Claude AI. ## Features - **Natural Language Queries**: Execute natural language queries against entity data using the `/entity/natural_query` endpoint - **JWT Authentication**: Secure access using Bearer token authentication - **Rate Limiting**: Built-in rate limiting to prevent API abuse - **Token Caching**: Efficient token validation with caching - **Error Handling**: Comprehensive error handling with detailed error messages - **Retry Logic**: Automatic retry with exponential backoff for failed requests ## Tools ### 1. `set_auth_token` Set the JWT Bearer token for authentication with the Ambivo API. **Parameters:** - `token` (string, required): JWT Bearer token **Usage:** ```json { "token": "your-jwt-token-here" } ``` ### 2. `natural_query` Execute natural language queries against Ambivo entity data. **Parameters:** - `query` (string, required): Natural language query describing what data you want - `response_format` (string, optional): Response format - "table", "natural", or "both" (default: "both") **Example queries:** - "Show me leads created this week" - "Find contacts with gmail addresses" - "List opportunities worth more than $10,000" - "Show me leads with …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.