FlowCheck MCP Server
Acts as a production-grade safety layer for AI-assisted coding, monitoring Git hygiene, scanning for security issues (PII, secrets, injection), and enabling semantic history search.
README
FlowCheck MCP Server
<div align="center">
🛡️ Production-Grade Safety Layer for AI-First Development
Git hygiene monitoring + Security scanning + Semantic search + Full observability
</div>
Why FlowCheck?
AI coding assistants are incredibly productive—but they can also create massive, hard-to-review changesets and security risks. FlowCheck is a production-grade safety layer that:
- 🔍 Monitors Git state in real-time during AI-assisted coding
- 🔒 Scans for security issues (PII, secrets, prompt injection attacks)
- 🔎 Semantic history search - find commits by meaning, not keywords
- 📊 Tracks flow health (time, lines, branch age, drift from main)
- 📝 Full observability (OpenTelemetry traces, audit logs)
- 🎯 Intent validation (ticket-to-diff alignment)
- 🤖 Designed for AI agents with enforceable rules
Think of FlowCheck as a "smart fitness watch with a biometric lock" for your codebase—it helps you code faster while actively defending against security threats.
AI-First Design
FlowCheck is built specifically for the agentic coding workflow:
flowchart LR
Agent["🤖 AI Agent<br/>(Claude, Cursor, etc)"]
FC["🛡️ FlowCheck<br/>MCP Server"]
Git["📁 Git Repo<br/>(.git)"]
Agent -->|"get_flow_state()"| FC
FC -->|"analyze"| Git
Git -->|"metrics"| FC
FC -->|"status: warning<br/>security_flags: [...]"| Agent
Agent -->|"⏸️ Pause & suggest<br/>checkpoint commit"| Agent
Agent Rules (Recommended)
Copy rules/flowcheck-rules.md to your AI tool's rules directory:
# For Cursor
cp rules/flowcheck-rules.md .cursor/rules/
# For Claude Projects
cp rules/flowcheck-rules.md .claude/rules/
# For other tools
cp rules/flowcheck-rules.md .agent/rules/
This instructs AI agents to automatically check Git hygiene before starting tasks and to pause when thresholds are exceeded.
Quick Start
Installation
git clone https://github.com/backslash-ux/flowcheck.git
cd flowcheck
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
Claude Desktop Integration
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"flowcheck": {
"command": "/path/to/flowcheck/.venv/bin/python",
"args": ["-m", "flowcheck.server"],
"env": {
"PYTHONPATH": "/path/to/flowcheck/src"
}
}
}
}
MCP Tools
Core Tools
| Tool | Purpose |
|---|---|
get_flow_state |
Returns metrics + security_flags (PII/injection) |
get_recommendations |
Returns actionable nudges + security warnings |
set_rules |
Dynamically adjust thresholds |
v0.2 Smart Features (New)
| Tool | Purpose |
|---|---|
search_history |
Semantic search - find commits by meaning |
verify_intent |
Smart Intent Verification - use "AI Judge" (BYOK LLM) to align diffs with tickets |
sanitize_content |
PII/secret redaction before sharing with AI |
Example: verify_intent (Smart Mode)
{
"alignment_score": 0.4,
"is_aligned": false,
"ticket_id": "42",
"scope_creep_warnings": ["Scope Creep Detected by AI Judge"],
"reasoning": "The ticket asks for a bug fix in auth, but the diff contains a full refactor of the billing module."
}
Configuration
FlowCheck supports hierarchical configuration:
- Repo Config:
.flowcheck.json(in project root) - Global Config:
~/.flowcheck/config.json - Defaults
.flowcheck.json Example
{
"max_minutes_without_commit": 45,
"intent": {
"provider": "openai",
"model": "gpt-4o",
"api_key_env": "OPENAI_API_KEY"
}
}
Ignoring Files (.flowcheckignore)
Create a .flowcheckignore file in your repo root to exclude files from analysis (uses gitignore syntax):
tests/fixtures/
*.min.js
legacy/
Security Features
Guardian Layer
- PII Detection: Emails, phone numbers, SSNs, credit cards
- Secret Scanning: AWS keys, GitHub tokens, API keys, passwords
- Injection Filtering: Detects prompt injection attacks in diffs
Observability
- OpenTelemetry Traces:
gen_ai.*semantic conventions - Audit Logs: Append-only JSON Lines format in
~/.flowcheck/audit.log - All tool invocations are logged with trace IDs
Semantic Search
- TF-IDF Vectorization: No external ML dependencies
- SQLite Storage: Local index in
~/.flowcheck/semantic_index.db - Find commits by meaning, not just keywords
Installation & Deployment
Option 1: Docker (Recommended)
Get FlowCheck running in 30 seconds:
# Clone and setup
git clone https://github.com/backslash-ux/flowcheck.git
cd flowcheck
# Configure environment
cp .env.example .env
nano .env # Add your API keys
# Start the stack
docker-compose up
FlowCheck is now running at http://localhost:8000
See Docker Deployment Guide for:
- Local development setup
- Production deployment
- Image variants (production/slim/dev)
- Troubleshooting
Option 2: Python Package
pip install git+https://github.com/backslash-ux/flowcheck.git
# Set environment variables
export ANTHROPIC_API_KEY=sk-ant-xxxxx
# Start server
flowcheck-server
Option 3: From Source
git clone https://github.com/backslash-ux/flowcheck.git
cd flowcheck
# Create virtual environment
python3 -m venv .venv
source .venv/bin/activate
# Install in development mode
pip install -e ".[dev]"
# Run tests
pytest tests/
# Start server
flowcheck-server
Deployment
FlowCheck supports multiple deployment models:
| Scenario | Time | Guide |
|---|---|---|
| Local Development | 5 min | Docker |
| Production (Docker) | 10 min | Docker.md |
| Kubernetes | 30 min | Kubernetes.md |
| CI/CD Integration | 15 min | CI-CD.md |
👉 Deployment Guide for full options
Development
# Setup development environment
docker-compose -f docker-compose.dev.yml up
# Or use Python venv
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
# Run tests
pytest tests/ -v
# Run with coverage
pytest tests/ --cov=src/flowcheck
Philosophy
FlowCheck embodies the principle that good Git hygiene enables good AI collaboration:
- Smaller commits are easier for humans to review and audit
- Frequent checkpoints prevent losing work during long sessions
- Clean history makes it easier to understand what the AI changed
- Non-blocking nudges preserve developer autonomy
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 模型以安全和受控的方式获取实时的网络信息。