Api

com.politicalcomms由 politicalcomms.com 发布v0.2.1更新于 Nov 3, 2026

Compliant political SMS/MMS from MCP clients: projects, contacts, analytics, billing.

发布方自己的服务：Docs

已验证STDIO仅桌面沟通与协作数据与分析商业与电商

服务详情

标识符: com.politicalcomms/api
传输: STDIO
运行时: Desktop only
信任: Verified
发布于: Sep 16, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 politicalcomms.com。它以软件包形式运行，而不是托管端点，因此没有可与该域名比对的端点。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.politicalcomms%2Fapi.svg)](https://sourceweft.com/mcp/com.politicalcomms%2Fapi?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

面向 Political Comms API 的 MCP 服务器，让助手查看政治类短信/彩信项目、联系人、分析与账单，并创建、测试或安排发送。

可以做什么: 列出组织、层级、项目及项目配置
读取送达、互动、问卷与吞吐统计，以及消息统计和账单用量
浏览联系人列表、以 CSV 下载列表，并查看会话及其消息
查看邮件域名、发件人、列表、抑制名单、活动、统计与模板
创建、复制、测试、安排、暂停和取消安排短信/彩信项目，在会话中回复，并安排邮件活动或导入邮件列表
适用场景: 适合需要操作美国政治类短信/彩信账户的场景：在聊天客户端中查看项目、联系人列表与分析，或准备并安排合规的短信与邮件发送。
运行要求: 通过 npm 包以 stdio 在本地运行，需要 Node 20 或更高版本。需要 Political Comms API 密钥（前缀 pc_live_），通过环境变量 POLITICAL_COMMS_API_KEY 提供，并由人工在后台 Admin > API Keys 中创建。邮件写入工具需要组织具备邮件权限。

安装前请注意

API 密钥是实时凭据，通过环境变量传入。多个工具会作用于真实受众：test_project 会发送真实测试消息，schedule_project 会提交批量发送，reply_to_conversation 会发送真实回复，schedule_email_campaign 与 start_email_list_import 还需 confirm: true。发送可能产生费用；付费邮件流程仅在后台提供。服务器不提供删除操作。

安装

在 SourceWeft 中

打开控制台中的 Api，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

@political-comms/mcp

MCP (Model Context Protocol) server for the Political Comms REST API. Lets Claude and other MCP clients inspect organizations, projects, contact lists, analytics, and billing, and create, test, and schedule compliant political SMS and MMS sends in the US.

Runs over stdio. Requires Node 20 or later and a Political Comms API key (created in the dashboard under Admin > API, prefixed pc_live_).

Setup

Claude Code

bash

claude mcp add political-comms \  --env POLITICAL_COMMS_API_KEY=pc_live_... \  -- npx -y @political-comms/mcp

claude mcp add political-comms \  --env POLITICAL_COMMS_API_KEY=pc_live_... \  -- npx -y @political-comms/mcp

Claude Desktop

Add to claude_desktop_config.json:

json

{  "mcpServers": {    "political-comms": {      "command": "npx",      "args": ["-y", "@political-comms/mcp"],      "env": {        "POLITICAL_COMMS_API_KEY": "pc_live_..."      }    }  }}

{  "mcpServers": {    "political-comms": {      "command": "npx",      "args": ["-y", "@political-comms/mcp"],      "env": {        "POLITICAL_COMMS_API_KEY": "pc_live_..."      }    }  }}

Tools

Read only:

Tool	Description
`list_organizations`	List organizations visible to the API key. Doubles as a credential check.
`get_hierarchy`	Full organization hierarchy tree with brands.
`list_projects`	List messaging projects, filterable by organization, brand, or campaign.
`get_project`	Full configuration of one project.
`get_project_stats`	Delivery and engagement stats for one project.
`get_project_survey_results`	Topline survey results for a survey project: per-question option counts and percentages, completion and dropoff rates. Returns a 409 `NOT_A_SURVEY` error for other projects.
`get_project_throughput`	Carrier-limit estimate for one project: recipients per carrier and how long AT&T takes (`will_pause` is always false).
`get_campaign_throughput`	A campaign's T-Mobile daily cap, use today, and AT&T per-minute rates.
`list_contact_lists`	Contact lists with counts and status.
`get_contact_list`	One contact list with import progress, analysis, and `downloads` URLs.
`download_contact_list`	A contact list as CSV text (`type` original or analyzed), truncated at 100,000 characters.
`get_message_stats`	Aggregate message stats for a date range.
`get_ledger_usage`	Billing usage for a date range.
`list_conversations`	Conversations with at least one inbound message, sorted by last inbound message.
`get_conversation`	One conversation: status, contact, message counts, last activity.
`list_conversation_messages`	Messages in one conversation, newest first.
`list_email_domains`	Email sending domains and their DNS verification status.
`get_email_domain`	One sending domain, including the DNS records to publish.
`list_email_senders`	Email sender identities (From addresses).
`list_email_lists`	Email lists with contact counts and status.
`list_email_suppressions`	Suppressed addresses at org, identity, or list scope.
`list_email_campaigns`	Email campaigns with status and audience counts.
`get_email_campaign`	One campaign, including `blocked`: why it will not schedule.
`get_email_campaign_stats`	Report tiles and per-link clicks.
`list_email_templates`	Saved email templates with subject and last-updated time.
`get_email_template`	One template including its full HTML body.

Write (each is annotated as non read-only; create_project, test_project, schedule_project, and reply_to_conversation additionally require confirm: true because they stage or send real messages):

Tool	Description
`create_project`	Create a draft messaging project.
`test_project`	Send real test messages to explicit phone numbers.
`schedule_project`	Commit a bulk send at a specific date and time.
`unschedule_project`	Remove a project's schedule.
`pause_project`	Pause a running or scheduled send; resume with `schedule_project`.
`copy_project`	Copy a project into a new draft (drops lists, schedule, and stats).
`reply_to_conversation`	Send a real reply (text, one `media_ids` entry for MMS, or both) inside an existing conversation. Requires `confirm: true`.
`schedule_email_campaign`	Commit an email send. Requires `confirm: true`.
`unschedule_email_campaign`	Return a scheduled campaign to a draft state.
`start_email_list_import`	Import a CSV of contacts into an email list. Requires `confirm: true`.

The server deliberately exposes no delete operations.

Email tools

Email write tools need the email entitlement on the organization and return 403 ENTITLEMENT_REQUIRED without it; reads are open. Paid and human-driven email workflows (AI drafting, result exports) and deliverability triage (pausing and resuming a live send) are dashboard features rather than tools: they cost money or need a human watching a send. There is no inbound email or inbox surface.

Errors

API errors are returned as tool errors with the machine readable code and a recovery hint. Rate limited requests (600 requests/minute per key) mention the X-RateLimit-Reset wait; authentication failures explain that a human must create a key in the dashboard.

Full API reference: docs.politicalcomms.com. OpenAPI spec: politicalcomms.com/openapi.json.