Monitor vs Clamp Sh MCP
A side-by-side look at the Monitor and Clamp Sh MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Monitor for monitoring work as a local process; choose Clamp Sh MCP for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Monitor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Choose Clamp Sh MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CLAMP_API_KEY. - You want tools like
traffic.overview, traffic.timeseries, traffic.compare.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 64/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Freemium | Freemium |
| Required env vars | None listed | CLAMP_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,309 | 2 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 24 |
| Full listing | View Monitor | View Clamp Sh MCP |
Tools & capabilities
Monitor tools
No tool names declared yet. Check the project README from the listing page.
Clamp Sh MCP tools 24
traffic.overviewPageviews, visitors, sessions, bounce rate, avg duration. Period comparison included.traffic.timeseriesAny core metric over time with automatic granularity (visitors, sessions, bounce rate, avg duration, or event counts).traffic.compareCompare any metric across two arbitrary periods. Returns absolute and percent delta.traffic.liveVisitors active in the last N minutes plus their top pages, referrers, and countries.breakdownGroup visitors and pageviews by any dimension: `pathname`, `referrer_host`, `country`, `city`, `region`, `device_type`, `browser`, `browser_version`, `os`, `os_version`, `entry_page`, `exit_page`, `channel`, or any UTM field.pages.engagementPer-page metrics with `view`: `summary`, `engagement` (adds engagement seconds and bounce rate), `sections` (per-section view counts for one pathname; needs the section-views SDK extension).events.listCustom event counts with property filtering and grouping.events.observed_schemaThe actual fired-event signature with per-property type observations. Diff against a local `event-schema.yaml` to surface schema drift.events.property_valuesTop distinct string-typed values a property has taken on a specific event. Use to discover the value space before defining a cohort filter or running `events.list` with `property=`.revenue.sumSum Money-typed event properties. Split by currency, group by any dimension, switch to first-touch via `attribution_model`. Drill-in filters: `plan`, `product`, `first_touch_dim` + `first_touch_value`.revenue.summaryThe whole Revenue tab in one call: revenue per currency, customers, orders, AOV, LTV, MRR (running balance) + ARR, per-plan rollup (where `mrr_contribution` is the cumulative MRR balance per plan, not the in-period delta), per-product rollup, prior-period comparison, and mode flags (`is_subscriptio…revenue.retentionCohort revenue retention on MRR-on-MRR math. Per window: `mature_size`, `retained`, `retention_rate`, `mrr_at_d`, `baseline_mrr_mature`, `nrr` (net revenue retention; >1.0 = net expansion). Anchored at the customer's first `subscription_started`.- +12 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Monitor
{
"mcpServers": {
"betterdb-inc-monitor": {
"command": "npx",
"args": [
"-y",
"@betterdb/monitor"
]
}
}
}
Clamp Sh MCP
{
"mcpServers": {
"clamp-sh-mcp": {
"command": "npx",
"args": [
"-y",
"@clamp-sh/mcp"
],
"env": {
"CLAMP_API_KEY": "YOUR_CLAMP_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Monitor is categorized under Monitoring and uses a local stdio subprocess. Clamp Sh MCP belongs to Monitoring and uses a local stdio subprocess. Pick Monitor for monitoring work and Clamp Sh MCP for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Monitor is listed as freemium — a free tier with paid plans. Auth: api key required. Clamp Sh MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add betterdb-inc-monitor and clamp-sh-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Monitor has a quality signal of 64/100 (Good) with 5 views, 0 installs and 1,309 GitHub stars. Clamp Sh MCP has 55/100 (Good) with 3 views, 0 installs and 2 GitHub stars.