Granicus govDelivery MCP Server & Agent Skill

What is the Granicus govDelivery API, and what can an agent read from it?

Manages subscribers, topic subscriptions, categories and bulletins: create, schedule or send bulletins to topics and list sent bulletins. Payloads in the v1 API are XML. TMS sends and tracks email, SMS and voice.

• API: Communications Cloud (govDelivery) API; Targeted Messaging (TMS) API (REST)
• Access: Issued by your administrator
• Base URL: https://api.govdelivery.com/api/account/{ACCOUNT_CODE}/ (staging: https://stage-api.govdelivery.com/)
• Authentication: HTTP Basic authentication

Existing customers request API access from Granicus Customer Support (support@granicus.com), which provides credentials, an authorization token and a development environment. The account code comes from the admin interface.

The v1 API uses basic HTTP authentication with secure login credentials that have the needed govDelivery administrator permissions. Granicus support also issues an authorization token on request.

What can an agent read from Granicus govDelivery?

• Subscribers — Subscriber information resources: list subscribers and their details.
• Subscriber topic subscriptions — Which topics and categories a subscriber follows.
• Sent bulletins — List sent bulletins for the account.
• Topics and categories — Topic and category resources used to target bulletins.

What can an agent write to Granicus govDelivery?

• Send bulletin now — POST /api/account/{ACCOUNT_CODE}/bulletins/send_now sends immediately to subscribers of the listed topics. Confirm with the user first.
• Draft bulletin — POST /api/account/{ACCOUNT_CODE}/bulletins.xml saves a draft for administrator review.
• Add subscription — Adds topic subscriptions to a subscriber, creating the subscriber if needed.
• Delete subscription or subscriber — Removes topic subscriptions or deletes a subscriber record. Confirm with the user first.

Subscriber records are PII (email addresses and phone numbers). Bulletins are outward-facing public communications, so sends should require human approval.

How do I connect Granicus govDelivery to an AI agent over MCP?

As of October 2026 we found no MCP server published by Granicus itself.

The practical path is to host a small MCP server that wraps the Communications Cloud (govDelivery) API; Targeted Messaging (TMS) API, or to give the agent the calls directly with the SKILL.md below.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

For an API key or a service credential, one token connection at platform scope serves the whole organization; scope a connection to a single agent when that agent needs narrower access than the rest.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the Granicus govDelivery agent skill do?

The Granicus govDelivery skill is one SKILL.md file named iblai-connect-granicus. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the Granicus govDelivery SKILL.md

Save it as .claude/skills/iblai-connect-granicus/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against Granicus' documentation on October 20, 2026. Test it against your own Granicus govDelivery setup before you rely on it.

What can I ask a Granicus govDelivery agent to do?

• “Draft a bulletin about Saturday's road closure for the Public Works topic”
• “How many subscribers does our Emergency Alerts topic have?”
• “List the bulletins we sent last week and their subjects”
• “Subscribe resident@example.com to the Parks and Recreation topic”

How do I run a Granicus govDelivery agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the Granicus govDelivery MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

• AI agents for Government — what ibl.ai deploys in this sector

Which ibl.ai agents work with Granicus govDelivery data?

• Constituent Communications — Government

Which ibl.ai platform skills does a Granicus govDelivery agent use?

• /iblai-api-agent-mcp — MCP connectors for ibl.ai agents, end to end
• /iblai-vibe-agent-mcp — Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,…
• /iblai-api-agent-tool — Enable or disable an ibl.ai agent's tools via the platform API

What else should I know before connecting Granicus govDelivery to an AI agent?

Which other data sources can an AI agent connect to alongside Granicus govDelivery?

Which other Government systems have a connector?

• Accela Civic Platform — Permitting, licensing and code enforcement platform
• Esri ArcGIS — Geographic information system (GIS)
• PACER — U.S. federal court records system
• Salesforce Government Cloud — Government CRM and case management platform
• SAM.gov — Federal contracting and entity registration data
• ServiceNow — IT service management and workflow platform
• Tyler Data & Insights (Socrata) — Open data and government data platform
• Tyler Technologies — Public sector ERP, permitting and courts software
• USAspending.gov — Federal spending data

Every connector, grouped by sector, is on the connectors hub.