Publish Sign in

Analytics & Monitoring MCP Servers

949 Analytics & Monitoring MCP servers on Mcprush.

Browse stacks Start publishing

949 MCP servers

Scanned where there is a package or repository to read — the grade is on each server's page
Analytics & Monitoring

Analytics & Monitoring MCP servers on mcprush answer product, spend and reliability questions out of the warehouse and the observability stack, returning the cohort or the span the agent asked for rather than the dump around it.

What to look at before installing one is what a query costs and what the server may write back. A read tool pointed at a warehouse is a bill as well as a permission. Every server here names the publisher behind it and whether that publisher has been verified, the runtime it uses, how it authenticates, the tool surface it exposes and the price model it is sold under — and where a security scan has been run against it, what the scan found. The filters on the left narrow it further and the sort at the top decides what comes first.

Nearly every server in this catalogue is connected straight to its publisher: the listing gives the publisher’s own address or start command, and mcprush is not in the path, so nothing is routed, metered or billed here. The exception is a server delivered through the mcprush gateway — there one key covers everything installed against your account, the calls are metered where you can see them and the ceiling on what they may cost is yours to set, and installing it is a line of the mcprush CLI: npx mcprush@latest add, followed by the server’s id. The listing says which of the two it is before you install anything.

Compare
tick one more