OBSERVABILITY / Apache Software Foundation
Apache SkyWalking MCP Server
Queries a SkyWalking OAP you already run. The inspected install builds a local image; it does not pull a published one.
“server for integrating AI agents with Skywalking OAP and the surrounding ecosystem.”
01 / THE REASONING
Why this made the selection.
- The README lists concrete tools such as list_layers and list_services rather than a generic "observe the cluster" promise.
- The Docker path is `make build-image` and then a local skywalking-mcp:latest. That is a build, not a registry pull.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md
- 2026-10-14 reread of retained pinned setup/configuration evidence for the specific operational details added in this batch.
- Makefile
Our findings
- stdio example uses command "swmcp stdio" after a local build.
- Docker example runs skywalking-mcp:latest only after make build-image.
- README and Makefile agree on local architecture defaults and explicit ARM64 builds. The client example now separates executable and stdio argument rather than embedding both in command.
Not established by this review
- The image was not built.
- No OAP query was made.
- No authenticated session, installation, permission bypass or package-to-source parity test was performed.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
make build-imageCopying does not execute this command. It may retrieve a newer version than the reviewed source.
- Clone the reviewed SkyWalking MCP revision and enter its repository directory.
- Install the build prerequisites from that revision and run make build-image.
- Register the README Docker client block, with --sw-url changed to an OAP address reachable from inside the container.
- Add --sw-username and --sw-password if the OAP requires basic auth, and review its authorization boundary before use.
Before you start
- Go or Docker
- A SkyWalking OAP endpoint you are allowed to query
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"skywalking": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"skywalking-mcp:latest",
"--sw-url",
"http://localhost:12800"
]
}
}
}04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Server documentation ↗Checked
https://github.com/apache/skywalking-mcp/blob/ea491e1e0510d7fef2fac360ae80f38147e39baf/README.md
Supports: Install command and stated tools, summary, install, configExample, access, limitations, bestFor, review, compatibility, transports, license
- Repository licence ↗Checked
https://github.com/apache/skywalking-mcp/blob/ea491e1e0510d7fef2fac360ae80f38147e39baf/LICENSE
Supports: Redistribution terms
https://github.com/apache/skywalking-mcp/blob/ea491e1e0510d7fef2fac360ae80f38147e39baf/Makefile
Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports, license