Setup steps
Run the npm smoke test
Start with direct npx before editing client config. This proves the package can install and start in your local environment.
npx -y @modelcontextprotocol/server-everythingChoose the client JSON shape
Claude Desktop uses mcpServers, while VS Code examples often use servers. Copy the shape that matches the host you are testing.
"command": "npx", "args": ["-y", "@modelcontextprotocol/server-everything"]Restart and confirm the MCP surface
Fully quit the client, reopen it, then confirm tools, resources, prompts, and server logs appear before adding real data servers.
restart client -> inspect MCP logs -> remove lab server when doneTroubleshooting
The client hangs on first launch
npm is waiting for package install confirmation inside a non-interactive host.
Add -y before the package name and restart the client, not just the chat tab.
spawn npx ENOENT on Windows
The desktop app did not inherit the same PATH as your terminal.
Use command cmd with args ["/c", "npx", "-y", "@modelcontextprotocol/server-everything"].
Tools do not appear after editing JSON
The MCP host has not reloaded the config, or the JSON file has a trailing comma.
Validate the JSON, fully quit the client, reopen it, then inspect the MCP server log.
The search result mentions Everything Search
You are reading a different server built around the Windows Everything file search utility.
Check the exact package scope. This page is only for @modelcontextprotocol/server-everything.
HTTP command works, desktop stdio fails
You mixed transport tests with desktop-client config.
Use stdio for Claude Desktop or VS Code smoke tests unless your host explicitly supports HTTP transport.
What this server is, and what it is not
The official npm package describes Everything as an MCP server that exercises protocol features. That wording matters. The server exists to show whether an MCP client can handle tools, resources, prompts, sampling, and transport behavior. It does not claim to be a focused production integration for your filesystem, browser, database, issue tracker, or team memory.
Searchers using the exact phrase @modelcontextprotocol/server-everything npx are usually trying to answer one of four concrete questions: whether the package exists, whether npx is the right runner, why a desktop client fails on Windows, or whether the Everything reference server is safe to keep enabled. This page answers those questions directly instead of treating the query like a generic MCP explainer.
Use it when
You need to prove that Claude Desktop, VS Code, or another MCP host can start a server and expose the expected MCP primitives.
Do not use it when
You need durable production access to files, browsers, secrets, databases, or internal systems. Pick the narrow server for that workflow.
Command surface
Pick the command by launch environment
The package name stays stable. The wrapper changes based on whether your MCP host can launch npx directly.
First command to test
npx -y @modelcontextprotocol/server-everythingUse this for a local stdio smoke test when the MCP host can run npx directly.
Windows desktop wrapper
cmd /c npx -y @modelcontextprotocol/server-everythingUse this shape when a Windows desktop client cannot find npx from its own launch environment.
Explicit transport lab
npx @modelcontextprotocol/server-everything streamableHttpUse only when you are intentionally testing HTTP transport behavior in a controlled lab.
How to choose the right config shape
Choose the config by client and operating system, not by copying the first snippet that ranks. The same package can be represented in different JSON roots, and Windows desktop apps often need an explicit shell wrapper even when the same command works in a terminal.
Claude Desktop, macOS or Linux
Use this when Claude Desktop inherits a normal shell path and npx is available without a wrapper.
{
"mcpServers": {
"everything-lab": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-everything"]
}
}
}Claude Desktop, Windows fallback
Use this when the client log shows spawn npx ENOENT, command not found, or a silent launch failure on Windows.
{
"mcpServers": {
"everything-lab": {
"command": "cmd",
"args": ["/c", "npx", "-y", "@modelcontextprotocol/server-everything"]
}
}
}VS Code MCP server entry
Use this shape when VS Code expects a servers object rather than Claude Desktop mcpServers.
{
"servers": {
"everything-lab": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-everything"]
}
}
}Worked examples
Client smoke test before adding a real server
A team wants to know whether Claude Desktop can see MCP tools at all. They add the npx Everything entry, restart the client, confirm that tools and resources appear, then remove the entry before testing Filesystem or Memory. The success signal is client wiring, not production readiness.
Windows laptop where terminal works but the app fails
A developer runs npx in PowerShell successfully, but the desktop client logs spawn npx ENOENT. The fix is not another package. The fix is the Windows wrapper shape, because the app and terminal are launching commands from different environments.
Search confusion with Everything Search
A searcher sees an Everything MCP server that talks about Windows file indexing. That is not this package. This guide verifies the official scoped npm package and keeps file-search servers on a separate review path because file discovery can expose sensitive paths.
What to use after the Everything smoke test
Passing an Everything test means the client can talk to an MCP server. It does not mean every MCP server is safe. Use the next table to route the user to the correct AgentSkillsHub guide after the diagnostic command works.
You are building or testing an MCP client
Use Everything first
It exposes a broad protocol surface, so it is a good diagnostic server before connecting real data.
You want to let an assistant read local files
Use Filesystem instead
File access needs explicit allowed paths, narrower permissions, and a different safety checklist.
You want persistent project memory
Use Memory instead
Persistent memory changes retention, deletion, and privacy behavior. Everything is only a protocol exercise.
You want browser debugging
Use Chrome DevTools MCP instead
Browser inspection needs tab/session boundaries and a visible debugging workflow, not a generic reference server.
Frequently asked questions
What is @modelcontextprotocol/server-everything?
@modelcontextprotocol/server-everything is the official Everything reference server package for MCP client testing. It exercises prompts, resources, tools, sampling, and transport behavior so client builders can verify that an MCP host is wired correctly.
What npx command should I try first?
Start with npx -y @modelcontextprotocol/server-everything for a local stdio smoke test. The -y flag prevents the first run from waiting for npm package confirmation inside a desktop client.
Why does Windows sometimes need cmd /c?
Some desktop MCP hosts launch commands without the same shell path that your terminal uses. On Windows, wrapping the command as cmd /c npx -y @modelcontextprotocol/server-everything can make the launch path explicit.
Is Everything the same as Everything Search MCP?
No. The official package in this guide is @modelcontextprotocol/server-everything. Everything Search MCP servers usually refer to file-search integrations around the Windows Everything search utility, which is a different use case and a different risk model.
Can I use this server in production?
Usually no. Treat it as a reference and diagnostics server. If you need production file, browser, database, or memory access, choose a narrower server and review its owner, permissions, data paths, and rollback plan.
What should I check before copying a config snippet?
Check the exact package scope, npm latest version, binary name, client config shape, operating system wrapper, and whether the server belongs in a disposable test profile rather than your daily production profile.