PILLAR MCP Server
PILLAR is the first Revenue Architecture Operating System (RAOS) with a native MCP (Model Context Protocol) server. Query your revenue architecture — account health, pipeline, signals, renewals, scoring, plays, tasks, financial cascade, market intelligence, AI-generated narratives, and governed writes — directly from any AI assistant.Quick Start
1. Generate an API Key
Navigate to Settings > Integrations and scroll to the API Keys & MCP Server section. Click Generate API Key and save the key — it’s only shown once.2. Configure Your AI Assistant
Add the following to your Claude Desktop, Cursor, or VS Code MCP configuration:3. Start Querying
Ask your AI assistant natural language questions about your revenue data:- “What’s my pipeline summary?”
- “Which accounts are at risk this quarter?”
- “Show me critical signals and the top 3 save plays that have worked on similar accounts”
- “Simulate what NRR going from 108% to 115% would mean for ARR and AE headcount”
- “What’s the top expansion opportunity in the West territory right now?”
- “Ask PILLAR: who’s at risk of churning next quarter and why?”
Endpoint
Authorization header.
Available Tools (129)
PILLAR’s MCP surface spans 129 tools across 14 categories, covering every layer of the revenue architecture. The vertical_intelligence category (63 tools live) is the competitive moat — it carries PILLAR’s canonical district + federal-program datasets that horizontal Revenue AI platforms structurally cannot answer.Coverage as of May 2026: The vertical_intelligence category is backed by 51 jurisdictions (50 states + DC + federal) and 26 federal datasets (8 IPEDS components + 8 Higher Ed sources + 10 K-12 sources), exposed through 63 MCP tools. Per-district coverage is at 51/51 jurisdictions for assessment proficiency (5.03M cells across ~19,700 LEAs), cohort graduation (391k cells), accountability status (24k cells), and engagement/chronic absenteeism (104k cells) — the four priority district-grain tables. K-12 state funding allocations (NEW): 46 of 51 jurisdictions (90.2%), 114,699 per-LEA rows, 7.94B captured — IPEDS SFA per-institution state grant aid (3,669 institutions FY22-23 + 3,693 FY21-22) plus 11 state-specific programs (TX TEXAS Grant, CA Strong Workforce, 9 MI scholarship/grant programs). Per-state DOE deep ingest covers 27+ states at the recent-year grain; federal EDFacts SY 2020-21 backfill closes the long tail to 51/51 for the priority surfaces. The schema, ingest pipeline, MCP wrappers, and 550+ build-time-enforced Guarantees are runtime-truth — every commit blocks merge unless the canonical-shape validators (
G-X-31 through G-X-40) accept every row landing in the 26 federal-data + 47 state-funding tables. All Round 8 tools (Scorecard Field-of-Study, FSA CDR/GE/HCM/distress-score, SHEEO SHEF, NC-SARA, Carnegie 2025, IPEDS HR/ADM/AY/AL/EF-CIP, CCD School Universe, EDGE Locale, CRDC ×2, OSEP IDEA-B, McKinney-Vento, Title III, Migrant Ed, Perkins V, NSLP-CEP, NIEER) are live and MCP-callable today.src/lib/mcp/tool-catalog.ts, and new tools ship continuously as vertical-intelligence surfaces (K-12 state-calendar procurement windows, federal Title program eligibility, cooperative-contract lookups, NCES district enrichment, state DOE assessment + accountability + graduation) come online.
Tier 0 — Core Surface
The foundational tool set that shipped with the original MCP server. Still the most-invoked tier for day-to-day agent workflows.Core Intelligence
Operational
Data Readiness
Flywheel & Benchmarks
Connector Observability
Tier A — Plays, Tasks, Expansion (8 tools)
Plays Intelligence
Tasks & Activities
Expansion Whitespace
Tier B — Financial Cascade (9 tools)
Tier C — Market Intelligence (5 tools)
Tier D — AI Orchestration (7 tools)
Tier E — Scoring Transparency (5 tools)
Tier F — Governed Writes (5 tools)
Tier G — Vertical Intelligence (63 tools live)
The competitive moat. Horizontal revenue platforms (Salesforce, HubSpot, Gong, Clari) cannot ship these tools because they don’t maintain federal education datasets, accreditor calendars, per-state procurement timing, or canonicalized state DOE assessment data. PILLAR does — the Tier G surface answers questions the customer’s own procurement office and CFO operate in.
HigherEd — IPEDS institutional intelligence (UNITID-keyed)
K-12 — Federal Title dollars (NCES LEAID-keyed)
Public-sector — Procurement calendars + compliance
The canonicalization claim
PILLAR canonicalizes 51 jurisdictions (50 state DOEs + DC + federal) with a documented policy footprint, a structural honesty layer, and sixteen independent layers of accuracy verification: Round 1-5 reconciliation layer (closes “is the state-DOE proficiency number right?”)Each verification layer is a build-time-enforced Guarantee with a cited spec entry — see The Guarantee → Vertical Intelligence (X) for the full structural enforcement chain. Runtime-truth status (April 2026): 550 Guarantee tests pass on every commit; 0 route type errors; 26 federal datasets ingested with 890,000+ canonical rows ready for live upsert across 35 ingest scripts.Round 8 federal-data canonical-shape layer (closes “is the federal-dataset row right?”)
- Macro-level reconciliation against state-published statewide aggregates with 24-state coverage (
G-X-25)- Micro-level spot-checks against 17 hand-validated district fixtures across 13 states including the load-bearing LDOE R36→036 alias (
G-X-26)- External NAEP trend-direction cross-validation for the 11 Tier-1 states with a live MCP route at
/api/vertical/state-naep-comparison(G-X-27)- Silent-corruption canary on every ingested cell with queue-backed weekly review via the
value_unknown_alarmstable (G-X-28)- Federal Title pass-through reconciliation between EDFacts allocations and SEA-published disbursements (
G-X-29)- Per-district Title allocation spot-checks closing the loop on “we know proficiency AND federal allocation are right for the same district” (
G-X-30)
- IPEDS-extension shape discipline for Human Resources / Admissions / Academic Year Tuition / Academic Libraries / Enrollment by CIP — including biennial-even-year discipline on EF-CIP and pre-2014 collection_status discipline on Academic Libraries (
G-X-31)- OPEID padding integrity on the institution_crosswalk join — the only authorized path between UNITID-keyed (IPEDS, Scorecard, Carnegie) and OPEID-keyed (FSA CDR/GE/NSLDS/HCM, NC-SARA) datasets (
G-X-32)- College Scorecard shape validators on institution-level + field-of-study tables (
G-X-33)- Carnegie 2025 four-dimension derivation discipline —
is_r1/is_r2MUST be derivable fromresearch_activity_designation; SAEC eligibility flag MUST be true when SAEC classification is present (G-X-34)- FSA regulatory-status discipline preventing accidental publish-rate inference during the 2019-2023 GE rescission gap; CDR status enum + HCM level enum locked (
G-X-35)- SHEEO SHEF + NC-SARA state-level shape with USPS-keyed JSONB integrity (
G-X-36)- CRDC biennial discipline — collection year MUST be even; suspensions ≤ 2× total enrollment sanity check (
G-X-37)- CCD School Universe + EDGE locale enum — title_i_status, charter_status, magnet_status, virtual_indicator, locale_code all locked to documented value sets (
G-X-38)- OSEP IDEA Part B + K-12 federal program state-aggregate shape (
G-X-39)- NCES EDGE entity-type-conditional ID-length (school=12 / lea=7-10 / postsecondary=1-6 digits) + NIEER 0-10 quality benchmark hard cap (
G-X-40)
Why this differentiates PILLAR
State DOEs each express proficiency on a different scale, suppression with different sentinels, accountability in 4-tier vs 5-tier vs A-F, with subgroup labels that vary across all 51 jurisdictions. Each state DOE essentially publishes data that’s only legible inside its own bureaucracy. Without the canonicalization layer, a query like “show me districts with declining ELA proficiency under 50%, chronic absenteeism above 20%, and accountability rating in the bottom two tiers” is structurally impossible across state lines — every comparison would require state-specific knowledge of cut-scores, sentinels, and subgroup mappings. PILLAR’s vertical intelligence MCP layer makes that query a single tool call that runs in milliseconds and returns the unified answer with the comparability caveats baked in. Provenance + honest coverage limits. Every Tier G response carries row-levelsource strings and a response-level data_provenance section documenting reporting lag and known gaps. For example, get_district_title_allocations discloses the three dead-end paths that prevent national per-LEA II-A / IV-A coverage (the Q1 2026 ed.gov site reorg deleted the per-state workbooks; Internet Archive has zero XLSX snapshots of the ed.gov Title paths; USAspending.gov records only state-level primary awards and double-counts carryover obligations). Similarly, the per-state assessment ingestion documents per-state policy footprints (TN “Approached/Met/Exceeded” vs LA “Mastery and above” vs WI “Advanced+Meeting”) and surfaces continuity_break flags whenever year-over-year comparison crosses an assessment-family transition. Consumers should never guess at data availability — the route tells them what it has and what it doesn’t.
Compatible AI Assistants
PILLAR’s MCP server works with any MCP-compatible client:- Claude Desktop — Anthropic’s AI assistant
- Claude Code — CLI development assistant
- Cursor — AI-first code editor
- VS Code — GitHub Copilot with MCP support
- ChatGPT Desktop — OpenAI’s assistant
- Windsurf — Codeium’s AI editor
- Zed — High-performance editor with MCP
Security
- API keys are stored as SHA-256 hashes — the raw key is never persisted
- Each key is scoped to a single organization via Row-Level Security
- Keys can be revoked instantly from Settings > Integrations
- All data is org-scoped — you can only query your own organization’s data
- MCP server inherits PILLAR’s multi-tenant isolation
- All tools are defined in a single source-of-truth catalog at
src/lib/mcp/tool-catalog.tswhich both the external MCP server and the in-app Drafter runtime consume. No drift between surfaces.
Example Conversations
CRO Morning Briefing:
“What does my GTM health look like this morning?”
Claude calls get_dashboard → returns ARR, pipeline, at-risk accounts, signal count, forecast health
Renewal Review with NRR simulation:
“Which renewals are at risk in the next 30 days — and what would saving all of them do to NRR?” Claude callsAccount Deep Dive with Effectiveness:get_renewal_riskwithdays_out: 30→ totals at-risk ARR → callssimulate_nrr_impactwith current and projected NRR to show ARR uplift + AE-equivalent headcount
“Tell me about Houston ISD and recommend the best save play template for a district like this” Claude callsSignal Triage with Task Creation:search_accounts→get_account_360→get_play_effectivenessfiltered to the account’s segment/tier → recommends the highest-win-rate template with evidence
“Show me critical signals, acknowledge the top one, and create a follow-up task for the account owner” Claude callsProcurement-aware Forecast:get_active_signalswithseverity: "CRITICAL"→update_signal_status→create_taskwith source_type: “signal”
“What’s our forecast by procurement window instead of CRM stage?”
Claude calls get_procurement_forecast → explains the difference vs stage-based forecast → flags which deals are likely to slip based on procurement alignment
Board Briefing Generation:
“Generate a board-grade narrative for Tuesday’s meeting and pull the cohort retention curves to go with it” Claude callsScoring Credibility Check:generate_board_narrative→get_cohort_curves→ composes the pack
“How accurate has PILLAR’s renewal risk score been historically?”
Claude calls get_scoring_backtest → reports hit rate, false positives, and calibration drift
Connector Health Check:
“Are all my data sources syncing correctly?” Claude callsScore Provenance:list_connectors→get_sync_logfor any connectors showing errors
“Where does the health score for Houston ISD come from?”
Claude calls get_account_data_sources → returns which values came from CRM vs product analytics vs support tickets