Webhook Consumers and MCP
PrimeCal supports two complementary integration patterns:
- Webhook consumers for event-driven automation input/output.
- MCP tools/resources for AI-hosted interactive planning workflows.
Quick Decision Guide
Use webhooks when you need:
- push-style external trigger delivery
- one-way event fan-out to external systems
- signed payload verification and replay control
Use MCP when you need:
- live tool calling from AI hosts
- rich read/write context across calendars, tasks, profile, automation
- agent-scoped permission boundaries
Key Distinction
- Webhooks are automation transport primitives.
- MCP is a standards-compliant AI integration surface.
They can be combined, but they are not the same system.
Availability Model
PrimeCal MCP is permanently supported.
- No feature flag is required to turn MCP on.
- MCP is available whenever the PrimeCal MCP server endpoint/process is running with valid configuration.
- Access is controlled by agent profile permissions and API keys.
Webhook behavior and automation rule enablement are managed by automation-specific controls, independent of MCP availability.
Recommended Hybrid Pattern
- AI host calls MCP tools to read context and create/update planning artifacts.
- Automation rules react to those state changes.
- Webhook actions forward selected outcomes to external systems.
Example:
- MCP host creates a task in
Side projects. - Automation rule tags matching events/tasks and writes audit records.
- Webhook action posts summary payload to an external project board.