Engaging Networks MCP server
by dragosh29
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENGAGINGNETWORKS_REGION | No | The datacentre your account is on, from the spec's server list: `ca` (Canada / Europe, `https://ca.engagingnetworks.app/ens/service`, the default), `us` (`https://us.engagingnetworks.app/ens/service`) or `us2` (`https://us2.engagingnetworks.app/ens/service`). | ca |
| ENGAGINGNETWORKS_BASE_URL | No | Overrides the region's base URL. Used by the tests. | |
| ENGAGINGNETWORKS_API_TOKEN | Yes | The API User token. Required. An administrator of your Engaging Networks account creates the API user in the dashboard, gives it permissions (for example view permission on supporter data), and whitelists the IP address of the machine this server runs on. | |
| ENGAGINGNETWORKS_ALLOW_WRITES | No | `true` to register `update_supporter_opt_ins`. Off by default. |
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 issues