com.politicalcomms/api MCP Server

The MCP server com.politicalcomms/api provides compliant political SMS/MMS integration for MCP clients. It supports workflows involving projects, contacts, analytics, and billing, as indicated by its description. The server is intended to enable political messaging through tools exposed to an MCP client.

🛠️ Key Features

Compliant political SMS/MMS
Projects
Contacts
Analytics
Billing

🚀 Use Cases

Sending compliant political SMS/MMS from MCP clients
Managing political messaging via projects and contacts
Retrieving analytics related to SMS/MMS activity
Handling billing for messaging usage

⚡ Developer Benefits

Exposes messaging capabilities to MCP clients
Organized access patterns for projects, contacts, analytics, and billing

⚠️ Limitations

Limited details available beyond SMS/MMS, compliance scope, and the listed domains (projects, contacts, analytics, billing)

@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 Keys, 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 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_..."
      }
    }
  }
}

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.
`list_contact_lists`	Contact lists with counts and status.
`get_contact_list`	One contact list with import progress and analysis.
`get_message_stats`	Aggregate message stats for a date range.
`get_ledger_usage`	Billing usage for a date range.

Write (each is annotated as non read-only; create_project, test_project, and schedule_project 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.
`copy_project`	Copy a project into a new draft (drops lists, schedule, and stats).
`archive_project`	Archive a completed project.

The server deliberately exposes no delete operations.

Errors

API errors are returned as tool errors with the machine readable code and a recovery hint. Rate limited requests (100/min reads, 60/min writes, 30/min deletes 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.

License

MIT. Questions: support@politicalcomms.com

com.politicalcomms/api