MCP.so
登录

Pituitary MCP Server

@dusk-network

基本信息

分类

其他

传输方式

stdio

作者

dusk-network

提交者

Emanuele Francioni

关于 Pituitary MCP Server

Catch spec drift before it catches you. Pituitary indexes your specs, docs, and decision records, then detects overlap,

Pituitary MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "pituitary": {
      "command": "pituitary",
      "args": [
        "serve",
        "--config",
        ".pituitary/pituitary.toml"
      ]
    }
  }
}

Pituitary MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Pituitary?

Point Pituitary at your repository. 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.

How to use Pituitary?

Download the Pituitary binary from GitHub Releases and place it on your PATH. Generate a configuration file with pituitary init --path ., then build the index with pituitary index --rebuild. No API keys are required in deterministic mode.

Key features of Pituitary

  • Semantic search across indexed spec sections by domain and status.
  • Detect overlapping specs with similarity scores and relationship classification.
  • Side-by-side tradeoff analysis of two specs.
  • Trace impact of spec changes on specs, code refs, and docs.
  • Find stale docs relative to accepted specs with cited evidence.
  • Full composite review combining overlap, comparison, impact, drift, and remediation.

Use cases of Pituitary

  • 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.

评论

其他 分类下的更多 MCP 服务器