keep
★ 12.5k
vs
metamcp
★ 2.8k
keep vs metamcp
keep: Keep is an open-source AIOps and alert management platform designed to unify all your alerts and incidents. It offers a single pane of glass for alert deduplication, enrichment, filtering, correlation, and bi-directional integrations with various monitoring tools.; metamcp: MetaMCP is an MCP proxy designed to dynamically aggregate multiple MCP servers into a single unified server, applying custom middlewares. It serves as an infrastructure to host these composed MCP servers via a unified endpoint, compatible with any MCP client through SSE, Streamable HTTP, or OpenAPI.
01
TL;DR
keepObservability · ★ 12.5k
Centralizing and managing alerts from diverse monitoring systems.
metamcpObservability · ★ 2.8k
When to choose:
- You want one endpoint for many MCP servers, grouped into namespaces and served over SSE, Streamable HTTP or OpenAPI.
- You need API key or OIDC authentication and registration controls for a team.
- You want to remix tools with overrides and annotations and test them in a built-in inspector.
When to skip:
- You want a single binary: it needs Docker and a Postgres database.
- You need active maintenance: the README itself notes maintenance delays, and our data shows the last push on 2026-06-22.
- You are counting on pluggable middleware or MCP tool search: the README marks them as coming soon.
02
Side-by-Side Comparison
Field
Category
Observability
Observability
Stars
★ 12.5k
★ 2.8k
License
NOASSERTION
MIT
Install Command
git clone https://github.com/keephq/keep.git
docker compose up -d
Updated
2d ago
1w ago
Open Source
Yes
Yes
Tags
AIOps, Alert Management, Incident Response
MCP, Proxy, Orchestration
03
Features
01Single pane of glass for all alerts and incidents with customizable UI.
02Comprehensive alert processing including deduplication, correlation, filtering, and enrichment.
03Deep bi-directional integrations with monitoring tools and customizable workflows.
04Automation capabilities, akin to GitHub Actions, for monitoring tasks.
05AIOps 2.0 with AI-powered correlation and summarization for incidents.
01Dynamically aggregate MCP servers into namespaces and expose unified endpoints (SSE, Streamable HTTP, OpenAPI) with authentication.
02Apply pluggable middlewares at the namespace level to intercept and transform MCP requests/responses.
03Utilize an enhanced MCP inspector with saved server configurations for easy debugging of MetaMCP endpoints.
04Override tool names, titles, descriptions, and attach custom MCP annotations per namespace.
05Secure authentication with API keys, MCP OAuth, OpenID Connect (OIDC) provider support, and flexible registration controls.
04
Use Cases
↳Centralizing and managing alerts from diverse monitoring systems.
↳Automating incident response workflows and reducing alert fatigue.
↳Leveraging AI for intelligent alert correlation and incident summarization.
↳Aggregating and hosting multiple MCP servers under unified, authenticated endpoints with namespaces.
↳Remixing MCP servers by selecting specific tools and applying custom middlewares for observability and security.
↳Debugging MetaMCP endpoints and server configurations using its built-in enhanced inspector.
05
Best For
Most PopularEssentialTrending
EssentialTrending
FAQ
FAQ
What is the difference between keep and metamcp?
Both keep and metamcp are in the Observability category. keep has 12.5k stars, while metamcp has 2.8k stars.
Which is better, keep or metamcp?
The best choice depends on your use case. Choose keep if Centralizing and managing alerts from diverse monitoring systems., and metamcp if Aggregating and hosting multiple MCP servers under unified, authenticated endpoints with namespaces..
Is keep free or open source?
Yes, keep is open source on GitHub (NOASSERTION).
Is metamcp free or open source?
Yes, metamcp is open source on GitHub (MIT).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→