@transcend-io/mcp-server-consent

Retrieves consent records and preferences from Transcend's consent management platform through the Model Context Protocol, enabling LLM agents to query user consent states, consent history, and preference metadata without direct API calls. Uses MCP's standardized resource and tool interfaces to expose consent data as queryable endpoints that integrate seamlessly with Claude, other LLM clients, and multi-turn agent workflows.

Validates whether a user has active consent before executing data operations (e.g., sending marketing emails, processing personal data for analytics) by querying Transcend's consent state in real-time. Implements a gate pattern where LLM agents or downstream systems can check consent status synchronously before proceeding with a data action, returning a boolean or detailed consent object to inform conditional logic.

Exposes detailed consent metadata including timestamps, consent version, user agent, IP address, and full audit trail of consent changes through MCP resources. Allows agents and compliance tools to reconstruct the complete consent lifecycle for a user, supporting audit requirements and dispute resolution by providing immutable, timestamped records of when consent was granted, modified, or revoked.

Supports querying consent across multiple purposes, categories, or data processing activities in a single request, with optional filtering by status, date range, or consent version. Implements a flexible query interface that allows agents to retrieve consent for multiple related purposes (e.g., 'marketing AND analytics AND profiling') and filter results by consent state, enabling complex compliance checks without multiple round-trips.

Exports user consent data in structured formats (JSON, CSV) suitable for compliance reporting, data subject access requests (DSARs), or regulatory submissions. Implements a resource-based export pattern where agents can request consent data for one or multiple users and receive it in a format ready for documentation, audit, or regulatory filing without manual data transformation.

Enables agents to update consent status (grant, deny, withdraw) for specific users and categories through MCP tool calls, translating agent intent into Transcend API mutation requests. Implements request validation, idempotency handling, and audit logging to ensure consent changes are tracked and reversible.