mcp-mailchimp
Mailchimp MCP Pack — manage audiences, campaigns, and members via Mailchimp Marketing API.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
에이전트 강화
게시자의 자체 URL입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
https://gateway.pipeworx.io/mailchimp/mcp위의 Claude 버튼을 누르면 이름과 URL이 채워진 상태로 Claude가 열립니다. 확인은 Claude에서 직접 해야 합니다.
claude mcp add --transport http io.github.pipeworx-io-mailchimp https://gateway.pipeworx.io/mailchimp/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-mailchimp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/mailchimp/mcp" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
Mailchimp MCP Pack — manage audiences, campaigns, and members via Mailchimp Marketing API.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Mailchimp MCP Pack — manage audiences, campaigns, and members via Mailchimp Marketing API.
| Tool | Description |
|---|---|
mailchimp_list_audiences | View all audiences in your account. Returns audience names, member counts, and engagement stats. Use mailchimp_get_audience for detailed settings. |
mailchimp_get_audience | Get detailed settings and stats for a specific audience. Pass the audience ID (e.g., "abc123def456"). Returns name, member count, engagement metrics, and configuration. |
mailchimp_list_campaigns | View all email campaigns. Returns title, type (e.g., "regular", "automation"), status, and send timestamps. Use mailchimp_get_campaign for full details. |
mailchimp_get_campaign | Get full details of a campaign by ID (e.g., "abc123def456"). Returns settings, tracking configuration, performance stats, and send history. |
mailchimp_list_members | Get subscribers in an audience by ID (e.g., "abc123def456"). Returns email addresses, subscription status, and custom merge fields. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"mailchimp": {
"url": "https://gateway.pipeworx.io/mailchimp/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/mailchimp/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/mailchimp_list_audiences. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"mailchimp": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-mailchimp"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-mailchimp
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Mailchimp data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
Mailchimp MCP Pack — manage audiences, campaigns, and members via Mailchimp Marketing API.
{ "mcpServers": { "io.github.pipeworx-io-mailchimp": { "url": "https://gateway.pipeworx.io/mailchimp/mcp", "headers": {} } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 http 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
게시자가 등록한 환경 변수: PIPEWORX_API_KEY.
Mailchimp에는 HTTP로 연결합니다.
마지막 확인: 2026-11-10. Mailchimp MCP Pack — manage audiences, campaigns, and members via Mailchimp Marketing API.