Adversus Dialer MCP setup and connection checker
by jannikco
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIPMCP_API_KEY | Yes | PipMCP API key with connectors:read and connectors:call scopes. Set in the calling process environment. | |
| PIPMCP_CONNECTOR_ID | No | Connector ID. Leave unset to use adversus-dialer, or set to custom-api together with PIPMCP_INTEGRATION_ID when using a manually imported API. | adversus-dialer |
| PIPMCP_CONNECTION_ID | No | Explicit PipMCP connection ID from discovery, required for multiple accounts or when needed for a manually imported custom API. | |
| PIPMCP_INTEGRATION_ID | No | Explicit PipMCP integration ID, required for multiple accounts or when using a manually imported custom API. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues