Query Scouter APM (objects, counters, XLog transactions) over stdio via a Scouter collector.
Query Scouter APM (objects, counters, XLog transactions) over stdio via a Scouter collector. Exposed over MCP by the scouter mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A stdio MCP server that connects directly to a Scouter Collector over TCP and queries XLogs, counters, and objects. Its purpose is to let an AI quickly explore Scouter metrics and diagnose root causes. Each result carries txid / gxid / objName / endTimeIso, which you can use as keys to cross-analyze with other observability tools such as OpenSearch or Datadog.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
list_objects — List objects/agentssearch_xlog — Search XLogs (latency/errors)get_service_summary — Per-service aggregate (count/avg/max/p95/errorRate), top 50get_summary — Collector's daily pre-aggregated stats (top-50 SQL/service/error/... — no scanning)get_xlog_detail — XLog detail (SQL/bind params)get_xlog_by_gxid — Distributed-transaction groupget_counter — Counter time series (same-day, full resolution)get_counter_stat — Long-range counter stats (5-min resolution, up to 31 days)list_counters — Available counters for an objTypelist_alerts — Past collector alertsget_active_services — Services running right nowlist_threads — JVM thread list (state histogram + top 50 by cpu)You will need 5 environment variables: SCOUTER_COLLECTOR_HOST, SCOUTER_COLLECTOR_PORT, SCOUTER_USER, SCOUTER_PASSWORD, SCOUTER_TZ. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Scouter MCP's toolset — list_objects, search_xlog, get_service_summary and 11 more — is a fair guide to whether it matches your workflow. It is maintained by 335; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_objects | List objects/agents |
| search_xlog | Search XLogs (latency/errors) |
| get_service_summary | Per-service aggregate (count/avg/max/p95/errorRate), top 50 |
| get_summary | Collector's daily pre-aggregated stats (top-50 SQL/service/error/... — no scanning) |
| get_xlog_detail | XLog detail (SQL/bind params) |
| get_xlog_by_gxid | Distributed-transaction group |
| get_counter | Counter time series (same-day, full resolution) |
| get_counter_stat | Long-range counter stats (5-min resolution, up to 31 days) |
| list_counters | Available counters for an objType |
| list_alerts | Past collector alerts |
| get_active_services | Services running right now |
| list_threads | JVM thread list (state histogram + top 50 by cpu) |
| get_thread_detail | Live thread of an ACTIVE transaction (stack/lock owner/current SQL) |
| get_object_env | Agent JVM system properties (secrets masked) |
{
"mcpServers": {
"scouter-prod": {
"command": "java",
"args": ["-jar", "/ABSOLUTE/PATH/scouter-mcp-<version>-all.jar"],
"env": {
"SCOUTER_COLLECTOR_HOST": "prod-collector", "SCOUTER_COLLECTOR_PORT": "6100",
"SCOUTER_USER": "prod-user", "SCOUTER_PASSWORD": "***", "SCOUTER_TZ": "Asia/Seoul"
}
},
"scouter-stg": {
"command": "java",
"args": ["-jar", "/ABSOLUTE/PATH/scouter-mcp-<version>-all.jar"],
"env": {
"SCOUTER_COLLECTOR_HOST": "stg-collector", "SCOUTER_COLLECTOR_PORT": "6100",
"SCOUTER_USER": "stg-user", "SCOUTER_PASSWORD": "***", "SCOUTER_TZ": "Asia/Seoul"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SCOUTER_COLLECTOR_HOST | Endpoint or connection string the server talks to. | Optional |
| SCOUTER_COLLECTOR_PORT | Configuration value read at startup. | Optional |
| SCOUTER_USER | Configuration value read at startup. | Optional |
| SCOUTER_PASSWORD | Configuration value read at startup. | Optional |
| SCOUTER_TZ | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.