Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.
Self-hosted AI teammate in Slack: @mention it and Claude Code or Codex investigates CloudWatch logs, runs tests, and opens pull requests. The bundled MCP server holds all credentials (GitHub, AWS, Slack) so the agent never sees keys. One-command deploy to your own AWS. MIT.
MCP server that connects your IDE or AI assistant to Codex CLI for code analysis and editing with support for multiple models (gpt-5-codex, o3, codex-1)
Quality signal
43/100 (Fair)
49/100 (Fair)
Install path
npx · high
npx · high
Engagement
0 0 0 2
0 0 0 23
Tools
Not listed yet
File referencing syntax for code analysis (e.g., @src/, @package.json)Multi-turn session management with context preservationSandbox mode with explicit approval policies for safe automationStructured change mode producing OLD/NEW patch outputsSupport for local OSS models via Ollama or LM StudioWeb search integration for research within prompts
