Eds MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 169 installs a week from npm. Last commit 18 Aug 2026.
41 tools for Adobe Edge Delivery Services: read, audit, track, monitor, fix, publish, undo — safely.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(command, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add eds-mcp-server -e 'EDS_OWNER=<EDS_OWNER>' -e 'EDS_REPO=<EDS_REPO>' -- npx -y @focusgts/eds-mcp-server{
"mcpServers": {
"eds-mcp-server": {
"command": "npx",
"args": [
"-y",
"@focusgts/eds-mcp-server"
],
"env": {
"EDS_OWNER": "<EDS_OWNER>",
"EDS_REPO": "<EDS_REPO>"
}
}
}
}[mcp_servers.eds-mcp-server]
command = "npx"
args = ["-y", "@focusgts/eds-mcp-server"]
env = { EDS_OWNER = "<EDS_OWNER>", EDS_REPO = "<EDS_REPO>" }{
"mcpServers": {
"eds-mcp-server": {
"command": "npx",
"args": [
"-y",
"@focusgts/eds-mcp-server"
],
"env": {
"EDS_OWNER": "<EDS_OWNER>",
"EDS_REPO": "<EDS_REPO>"
}
}
}
}{
"servers": {
"eds-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@focusgts/eds-mcp-server"
],
"env": {
"EDS_OWNER": "<EDS_OWNER>",
"EDS_REPO": "<EDS_REPO>"
}
}
}
}Put your own values in place of
<EDS_OWNER> (GitHub org/user that owns the EDS site repo), <EDS_REPO> (GitHub repository name for the EDS site).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
EDS_REF (Git branch (default: main)), EDS_API_KEY (Admin API key for preview/publish/cache operations), EDS_DOMAIN_KEY (OpTel domain key for Core Web Vitals, 404s, and experiment queries), EDS_DA_TOKEN (Document Authoring IMS access token — enables the eds_da_* source and bulk tools), EDS_DA_ORG (Document Authoring org (defaults to EDS_OWNER)), EDS_DA_REPO (Document Authoring repo/site (defaults to EDS_REPO)).
Alternatives to Eds MCP Server
same job, measured the same wayAI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.
Public read-only demo of Netmon's network monitoring tools over a recorded snapshot.
Transparent audit proxy for MCP servers: logs every tool call, flags poisoning and rug pulls.
Kiln MCP server for agents: design, slice, print, monitor, and recover physical objects safely.
MCP server for Microsoft Entra ID sign-in and audit-log triage (read-only by default)
An MCP server that provides tools for managing and monitoring your Fleet Device Management instance.
MCP for ROS 2 monitoring, debugging, and managing nodes, topics, services, and TF2 frames.
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
Eds MCP Server — questions
Answers built from our own checks of this server.