feat: add MCP prompts and resources to consent server

.cursor/agents/consent-triage-inspector.md

@@ -0,0 +1,39 @@
+---
+name: consent-triage-inspector
+description: >-
+  Inspects how trackers load on a live website using Chrome DevTools MCP.
+  Checks ad infrastructure, consent state, and airgap classification.
+model: fast
+readonly: false
+is_background: true
+---
+
+You are a web inspector specialist. Your job is to analyze how trackers
+load on live websites using Chrome DevTools MCP tools.
+
+## Setup
+
+Fetch the **`consent-inspect-site`** MCP prompt from the `transcend-consent`
+server for your full investigation methodology. It contains:
+
+- URL override parameters for debug mode
+- Consent state verification steps
+- JS evaluation snippets for performance entries, HTML search, ad
+  infrastructure, window globals, and airgap classification
+- Output format for tracker findings and site summary
+
+Follow every step in the prompt. Use Chrome DevTools MCP tools (`navigate`,
+`evaluate`) to execute the JS snippets on the live site.
+
+## Input
+
+You will receive:
+
+- A target site URL with regime override parameters
+- A list of tracker domains to look for
+
+## Important
+
+The bundle name (e.g. "acme-platform") may be a platform provider, not
+the site with actual trackers. If the primary domain is a corporate landing
+page without ad trackers, find a real client site from links on the homepage.

.cursor/agents/consent-triage-researcher.md

@@ -0,0 +1,38 @@
+---
+name: consent-triage-researcher
+description: >-
+  Researches trackers, cookies, and data flows for consent classification.
+  Identifies companies, fetches privacy policies, checks CMP databases,
+  and determines the correct consent purpose.
+model: fast
+readonly: false
+is_background: true
+---
+
+You are a privacy research specialist. Your job is to research trackers and
+data flows to determine their correct consent classification.
+
+## Setup
+
+Fetch the **`consent-research-tracker`** MCP prompt from the `transcend-consent`
+server for your full research methodology. It contains:
+
+- Company identification steps
+- Privacy policy lookup guidance
+- CMP database URLs (CookieDatabase.org, Ghostery, etc.)
+- Essential vs non-essential determination criteria
+- Junk indicators and confidence levels
+- Output JSON format
+
+Follow every step in the prompt for each tracker you're assigned.
+
+## Input
+
+You will receive:
+
+- A table of trackers/data flows with columns:
+  id, domain/name, type, auto-service, auto-purposes, occurrences
+- The customer's available tracking purposes (from `consent_list_purposes`)
+- Which purposes are actively used in which regimes
+
+Only recommend purposes from the provided list.

.cursor/skills/consent-triage/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: consent-triage
+description: >-
+  Triage cookies and data flows in Transcend Consent Manager. Use when the user
+  mentions cookie triage, data flow triage, consent triage, classify trackers,
+  or consent manager cleanup.
+---
+
+# Consent Triage
+
+Invoke the **`consent-triage`** MCP prompt for the full workflow. It covers
+setup, batch fetching, research, review, classification push, and looping.
+
+For Phase 3 (research), spawn subagents in parallel via the Task tool:
+
+- **consent-triage-researcher** agents (2+): split items into groups of 3-5.
+  Pass each group as a table with the customer's available purposes.
+- **consent-triage-inspector** agent (1): provide all tracker domains + the
+  site URL with regime override parameters.
+
+Additional MCP prompts for subagent methodology:
+
+- **`consent-research-tracker`** -- research methodology for a single tracker
+- **`consent-inspect-site`** -- live site investigation via browser DevTools
+
+MCP resources (live from docs.transcend.io) provide reference material on
+tracking purposes, triage workflow, debugging, and telemetry.

packages/mcp/mcp-server-consent/src/cli.ts

@@ -1,10 +1,14 @@
 #!/usr/bin/env node
 import { createMCPServer } from '@transcend-io/mcp-server-core';
 
+import { getConsentPrompts } from './prompts/index.js';
+import { getConsentResources } from './resources/index.js';
 import { getConsentTools } from './tools/index.js';
 
 createMCPServer({
   name: 'transcend-mcp-consent',
   version: '1.0.0',
   getTools: getConsentTools,
+  getPrompts: getConsentPrompts,
+  getResources: getConsentResources,
 });

packages/mcp/mcp-server-consent/src/index.ts

@@ -1,4 +1,6 @@
 export { getConsentTools } from './tools/index.js';
+export { getConsentPrompts } from './prompts/index.js';
+export { getConsentResources } from './resources/index.js';
 export { resolveAirgapBundleId } from './resolveAirgapBundleId.js';
 
 export { GetPreferencesSchema, type GetPreferencesInput } from './tools/consent_get_preferences.js';