Waalaxy MCP Server
Server 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 |
|---|---|
| get_campaignsC | Get all campaigns from Waalaxy |
| get_campaign_statsC | Get statistics for a specific campaign |
| get_prospectsB | Get prospects from a campaign or list |
| get_conversationsC | Get LinkedIn conversations from Waalaxy inbox |
| get_analyticsC | Get account analytics and statistics |
| close_sessionA | Close browser session and clean up resources |
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 6 tools
Each tool has a clearly distinct purpose: session management, analytics, campaigns listing, campaign stats, conversations, and prospects. No overlap or ambiguity.
All tools consistently use the verb_noun pattern with lowercase and underscores. Verbs are either 'close' or 'get', which is predictable and clear.
With 6 tools covering the core functionalities of a Waalaxy automation server (campaigns, prospects, conversations, analytics, session), the count is well-scoped and each tool earns its place.
The tool surface is heavily read-only, missing write operations for campaigns (create, update, delete), prospects (create, update, delete), and conversations (send messages). This severely limits automation capabilities.