Ambivo MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| natural_queryA | Execute natural language queries against Ambivo entity data. This tool processes natural language queries and returns structured data about leads, contacts, opportunities, and other entities. |
| set_auth_tokenA | Set the authentication token for API requests. This must be called before using other tools to authenticate with the Ambivo API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one handles authentication setup, the other executes queries. No overlap or confusion possible.
Both tools use consistent snake_case naming, and each name clearly indicates its function ('set_auth_token' for authentication, 'natural_query' for querying).
Only 2 tools for a domain that involves multiple entities (leads, contacts, opportunities). This is insufficient to cover typical operations, though the natural_query tool may encapsulate many actions.
The server claims to handle leads, contacts, and opportunities, but provides no CRUD tools or entity-specific operations. A single query tool is severely incomplete for data management tasks.