Pituitary
Catch spec drift before it catches you. Pituitary indexes your specs, docs, and decision records, then detects overlap,
contradictions, stale docs, and code that drifts from what was decided.
6 tools for spec-aware AI workflows:
- search_specs: semantic search across indexed spec sections
- check_overlap: detect specs that cover overlapping ground
- compare_specs: side-by-side tradeoff analysis of two specs
- analyze_impact: trace which specs, docs, and code paths are affected when a spec changes
- check_doc_drift: find docs that contradict accepted specs
- review_spec: full composite review (overlap + comparison + impact + drift + remediation)
Single Go binary. One SQLite file. No API keys required. Deterministic by default.
Overview
What it does
Point Pituitary at your repo. It indexes your specs, docs, and decision records, then catches what you can't track by hand. What you wrote down should still be true. Pituitary makes sure it is.
Tools
| Tool | Description |
|---|---|
| search_specs | Semantic search across indexed spec sections. Filter by domain and status. |
| check_overlap | Detect specs that cover overlapping ground. Returns similarity scores and relationship classification. |
| compare_specs | Side-by-side tradeoff analysis of two specs. |
| analyze_impact | Trace which specs, code refs, and docs are affected when a spec changes. |
| check_doc_drift | Find docs that have gone stale relative to accepted specs, with cited evidence. |
| review_spec | Full composite review: overlap + comparison + impact + drift + remediation. |
Requirements
- Pituitary binary on PATH (download from GitHub Releases)
- A config file (generate one with
pituitary init --path .) - A built index (
pituitary index --rebuild)
No API keys required in deterministic mode.
Use cases
- PR review: Agent calls check_overlap and analyze_impact when a PR touches specs or decision records
- Pre-merge drift check: Agent calls check_doc_drift to surface stale docs before merging
- Decision authoring: Agent calls review_spec to get a full assessment of a new or changed spec
- Impact questions: "What specs and docs would be affected if I change the auth middleware?" triggers analyze_impact
Links
Server Config
{
"mcpServers": {
"pituitary": {
"command": "pituitary",
"args": [
"serve",
"--config",
".pituitary/pituitary.toml"
]
}
}
}Project Info
Created At
2 months agoUpdated At
2 months agoAuthor Name
autholykosStar
-Language
-License
-Recommend Servers
View AllAirtreks Mcp
@SEKeener
a day ago
Mcp Server Chatsum
@chatmcp
summarize chat message
typescript
a year ago
Amap Maps
@amap
高德地图官方 MCP Server
a year ago
Playwright Mcp
@microsoft
Playwright MCP server
TypeScript
10 months ago