Greenhouse Ops Control Plane
Recruiting-ops MCP for Greenhouse: referral SLA misses, funnel movement, stale candidates, overdue feedback, unfilled openings, stage conversion, source quality, and bottleneck owners inside an MCP client.
README
TA Ops Agent
This is a trust-first recruiting ops operating system, packaged here as a public-safe repo for working on reliable AI operations over noisy enterprise data.
The system combines deterministic data extraction, LLM synthesis, trust gating, and role-scoped delivery to turn messy ATS workflows into actionable daily digests. The interesting part is not "AI for recruiting." The interesting part is how the repo separates what must be true in code from what can be synthesized by a model.
Why this repo is interesting
- Deterministic and probabilistic responsibilities are split on purpose.
- MCP integrations expose a large real-world API surface in a reusable way.
- Trust gates prevent low-confidence joins from driving live personalized delivery.
- The demo is public-safe and runs on sanitized fixtures with no secrets.
- Every major step is observable: snapshots, audits, digests, tests, and chart stubs.
Architecture
ATS MCP data -> deterministic snapshot -> attribution audit -> LLM synthesis
-> trust gates -> Slack digest / dashboard chart / operator review
Read more in docs/architecture.md and docs/evaluation-and-safety.md.
For the canonical output identity and Slack-vs-dashboard-vs-role-report split, see docs/magellan-output-doctrine.md.
For the current implementation checkpoint and shipped-vs-future-state status, see docs/current-state-checkpoint.md.
For the future-state rebuild, see docs/magellan-v2-architecture.md.
For phased implementation sequencing, see docs/magellan-v2-execution-roadmap.md.
For the key unresolved architecture and product calls, see docs/magellan-v2-open-decisions-register.md.
For the live pilot metric policy, see docs/pilot-metric-catalog.md.
For the reviewed pilot operating procedure, see docs/pilot-service-runbook.md.
Current state
Today, Magellan already has:
- reviewed-release-driven Slack and dashboard delivery
- a Live-first product shell
- persona-specific operating surfaces
- weekly role progress reports as first-class release artifacts
- presentation-doctrine checks enforced in preflight
The biggest things that are still future-state are:
- the normalized V2 data core
- fully extracted identity / attribution / coordinator subsystems
- a persisted recruiter approve/send workflow for role reports
- a first-class operator console
See docs/current-state-checkpoint.md for the canonical checkpoint.
Public Demo
The public repo ships with a sanitized demo pack in demo/.
# start the local chart + demo server
./scripts/ta-demo-server
# inspect the latest sanitized snapshot
./scripts/ta-snapshot show
# generate a recruiter digest from fixture data
./scripts/ta-demo-digest --persona recruiter --dry-run
# generate a coordinator digest from fixture data
./scripts/ta-demo-digest --persona coordinator --date 2026-04-03 --dry-run
# run a fail-closed release preflight before preview or live sends
./scripts/ta-preflight --scope preview --personas recruiter,coordinator --skip-tests --skip-analytics
# build private live demo artifacts, then preview a live recruiter digest
./scripts/ta-snapshot live-build
./scripts/ta-demo-digest \
--snapshot-dir "$PWD/reports/private/live-demo/snapshots" \
--date 2026-04-02 \
--recruiter avery-chen \
--send-to-sam
Default demo URLs are served from http://127.0.0.1:4173.
What is included
mcp/greenhouse/: Greenhouse Harvest v3 MCP server with retry logic and broad endpoint coveragemcp/slack/: Slack MCP server for DM delivery, allowlists, and Block Kit outputlib/: structured snapshot contract, normalization, and digest data helpersdemo/: sanitized fixtures, sample outputs, walkthrough, public demo server, and screenshotsdocs/: public architecture, evaluation, and framework notesscripts/: legacyta-*commands retained for compatibility
Snapshot Contract
The public-facing data model is the Snapshot contract in lib/snapshot-schema.ts.
The stored demo fixtures include:
recruiter_candidate_metricsrecruiter_role_metricscoordinator_watchlistattribution_auditblocking_reasonsallow_live_recruiter_digestallow_live_coordinator_digestsynthesis
This is intentional: public fixtures should already be complete and trustworthy, not repaired at read time.
Evaluation and Safety
Magellan highlights the control surfaces that matter in production:
- bounded retry logic for external APIs
- snapshot validation before downstream use
- preview-only gates when attribution is incomplete
- separate treatment of candidate ownership, role support, and low-confidence activity signals
- explicit blocking reasons attached to delivery decisions
The repo includes automated checks for fixture completeness, trust gating, CLI behavior, and chart rendering.
Private Demo Workflow
For real demo data, Magellan writes local-only artifacts under reports/private/live-demo/:
snapshots/snapshot-YYYY-MM-DD.jsonaudits/people-map-YYYY-MM-DD.jsonaudits/attribution-audit-YYYY-MM-DD.jsonaudits/coordinator-validation-YYYY-MM-DD.json
That private build path is intentionally separate from the public demo/fixtures/ directory.
./scripts/ta-snapshot live-build
MAGELLAN_SNAPSHOT_DIR="$PWD/reports/private/live-demo/snapshots" ./scripts/ta-snapshot validate
MAGELLAN_SNAPSHOT_DIR="$PWD/reports/private/live-demo/snapshots" ./scripts/ta-snapshot audit
Slack preview sends work against allowlisted users. If the Slack app token lacks users:read.email, use --send-to-sam for preview or pass --recipient-slack-id for explicit live sends.
For recruiter/coordinator pilot sends, keep real Slack IDs in the ignored config/team.local.json overlay. A tracked template lives at config/team.local.example.json, and ./scripts/ta-recipient-audit --run-id RUN_ID shows trusted vs live-ready recipients plus any unmapped pilot users.
./scripts/ta-preflight is the canonical operator gate before release approval. It checks artifact availability, reviewed release state, read-only audits, persona gates, digest dry-runs, and optional test/build readiness, then exits non-zero if the requested scope is not safe.
MCP Packages
Greenhouse MCP
72 read-only tools plus a narrow gated write surface for application assignment and recruiter/coordinator hiring-team ownership repairs.
- Auth: OAuth2 client credentials with token caching
- Pagination: cursor-based
- Rate limiting: 429-aware bounded retry
- Write safety:
- global kill-switch via
ENABLE_GREENHOUSE_WRITE_OPS=true - required actor allowlist via
GREENHOUSE_ALLOWED_WRITE_ACTOR_IDS - required human-readable audit reason
- explicit confirmation flags and
dry_run - no generic replace endpoint; only single-target repair tools
- global kill-switch via
- Runtime: TypeScript, Node.js 18+
Slack MCP
6 tools for DM delivery, user lookup, and preview-safe message sending.
- Safety:
DRY_RUNplusSLACK_ALLOWED_USERS - Output: plain text or Block Kit
- Runtime: TypeScript, Node.js 18+
Public-Safety Notes
- Private operational reports and real company data are not tracked in this public repo.
reports/now documents the boundary between public demo fixtures and private live artifacts.config/team.jsonis a sanitized example configuration.- The legacy
ta-*command names remain for backward compatibility, but the public product name is Magellan.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。