Apache SkyWalking MCP
Spec Support Unverified Confidence: Good (0.85)Apache SkyWalking MCP is an MCP server published by The Apache Software Foundation; its MCP spec-revision support has not been verified yet. It is the first-party server from The Apache Software Foundation. Last verified 2026-08-18.
Does Apache SkyWalking MCP support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Apache SkyWalking MCP supports (as of 2026-08-18).
Is Apache SkyWalking MCP a first-party (official) MCP server?
Yes. Apache SkyWalking MCP is the first-party MCP server published by The Apache Software Foundation (last verified 2026-08-18).
How do I connect to Apache SkyWalking MCP?
Apache SkyWalking MCP is available via the source repository at https://github.com/apache/skywalking-mcp. Authentication: none. Transports: stdio, streamable-http, sse-legacy.
When were Apache SkyWalking MCP's facts last verified?
2026-08-18. Each fact on this page links to the sources used to verify it.
Apache SkyWalking is an application performance monitoring system, and
skywalking-mcp is the project's own server for querying it from an
agent. It ships as a Go binary called swmcp that connects to a
SkyWalking OAP backend and exposes 16 tools across traces, logs, MQE
metric expressions, service metadata, events, alarms and four kinds of
topology query, plus ten prompts for guided analysis.
Deployment is self-hosted in every mode. The binary serves stdio,
streamable and sse subcommands, takes the OAP URL and credentials as
flags, and has a --read-only switch that restricts it to read
operations. There is no vendor-hosted endpoint, and the server does not
authenticate its own callers, which is why its 0.2.0 release added CORS
origin enforcement and DNS-rebinding protection for the HTTP transports.
Revision support is in an unusual state. The 0.3.0 section of the
changelog on master says the server migrated to the official
modelcontextprotocol/go-sdk and added support for the
2026-07-28 revision, answering both the per-request
_meta model and the legacy initialize handshake on one endpoint. No
0.3.0 release is tagged: the newest tag is v0.2.0. Because a changelog
entry on a default branch is not a shipped release, spec support is
recorded here as unverified, with the claim and its evidence on file for
the next check.
How widely adopted is Apache SkyWalking MCP?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: vendor-docs
· confidence 0.85 (Good).
- apache/skywalking-mcp README - "A Model Context Protocol (MCP) server for integrating AI agents with Skywalking OAP and the surrounding ecosystem"; the swmcp binary offers stdio, sse and streamable subcommands, a --read-only flag, and --sw-url / --sw-username / --sw-password for the OAP connection; documents 16 tools including query_traces, query_logs, execute_mqe_expression, list_services and query_services_topology, plus 10 prompts - accessed
- SkyWalking MCP CHANGES.md on master - the 0.3.0 section states the server "Migrated to the official modelcontextprotocol/go-sdk, adding support for MCP protocol version 2026-07-28. Clients on earlier revisions keep working: the server answers both the per-request _meta model and the legacy initialize handshake on the same endpoint"; the 0.2.0 section records the TLS-verification and CORS hardening - accessed
- apache/skywalking-mcp tags - only v0.1.0-rc0, v0.1.0 and v0.2.0 exist, so the 0.3.0 changelog section describes unreleased work; go.mod on master requires github.com/modelcontextprotocol/go-sdk v1.7.0 - accessed
- Official MCP Registry search for "skywalking" returned no records, so the server has no registry namespace - accessed