Skip to main content
Glama
Sign In

Mailchimp MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Mailchimp MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/mailchimp-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data are both labeled as the final workflow step and require identical setup, so it is not obvious when one should be used over the other. query_contexts is distinguishable as a metadata helper, but the core read/write operation boundary is muddy.

Naming Consistency4/5

execute_action, query_contexts, and query_data follow a consistent verb_noun snake_case pattern. prompts_menu is the only notable deviation, using a noun_noun form.

Tool Count4/5

Four tools is within a reasonable range and each has a role in the workflow. However, only two are operational tools, with one metadata helper and one prompt catalog browser.

Completeness3/5

The generic query/execute model can potentially cover Mailchimp reads and writes if the discovered action catalog is complete. Still, there are no explicit Mailchimp resource operations in the surface, so lifecycle coverage is indirect and opaque.

Available Tools

4 tools
execute_actionMailchimp Execute ActionA
Destructive
Inspect

Execute Mailchimp action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuMailchimp PromptsA
Read-only
Inspect

Browse the Mailchimp prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsMailchimp Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Mailchimp data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataMailchimp Data QueryA
Read-only
Inspect

Query Mailchimp data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • Mailchimp MCP

      damientilman
      A
      license
      A
      quality
      C
      maintenance
      Mailchimp MCP Server - Access Mailchimp data from Claude via MCP.
      100
      104 PyPI
      25
      MIT

    • Mailchimp MCP Server

      BusyBee3333
      A
      license
      C
      quality
      D
      maintenance
      Comprehensive MCP server for Mailchimp Marketing API v3.0 with over 104 tools and 15+ React UI apps, enabling management of campaigns, audiences, ecommerce, automations, reports, and more via natural language.
      100
      1
      MIT

    • MCP-manychat

      vdloureiro
      F
      license
      A
      quality
      D
      maintenance
      MCP server for ManyChat API integration that enables Claude and other AI assistants to manage subscribers, tags, custom fields, flows, and send messages through natural language.
      17
      -

    • gmail-multi-mcp

      in2guitar
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server exposing multiple Google Workspace Gmail accounts to Claude, with support for verified send-as aliases and opt-in sending.
      11 npm
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources