Available MCP tools

The Aigeon MCP server exposes one tool per logical operation. Tool names use snake_case; they map 1:1 to the underlying REST endpoints.

Contacts

| Tool | Description | Required API scope | | --- | --- | --- | | add_group_members | Add one or more contacts to a list. | contacts_access | | batch_update_custom_field | Set custom field values on a set of contacts. | contacts_access |

Sending

| Tool | Description | Required API scope | | --- | --- | --- | | send_email_through_flow | Enrol a contact into a flow and trigger the first email. | sending_access | | send_nb_email | Send a direct non-blocking transactional email. | sending_access |

Analytics

| Tool | Description | Required API scope | | --- | --- | --- | | get_org_stats | Top-level send / open / click / unsubscribe counts for the org. | analytics_access | | get_flow_campaign_summary | Stats for a specific flow's latest campaign. | analytics_access | | get_email_event_metric | Time-series data for a specific event type (open, click, etc.). | analytics_access |

Input / output shape

All tools accept plain JSON matching the REST request body (or query parameters for GETs). The response is the data field from the Aigeon JSON envelope — the wrapper code / status / message is handled by the MCP server internally and surfaced as a tool error if code != 0.

Extending the tool list

The MCP server reads its tool manifest from Aigeon's OpenAPI spec. New API endpoints automatically appear as tools on the next npx invocation (the server pulls the latest spec on startup). Pin a specific version with npx @aigeon/mcp-server@1.2.3 if you need stability across updates.