Home › Clients › VS Code › Reference & Testing

VS Code: Reference & Testing

VS Code setup for Reference & Testing. 3 indexed servers in this category, 0 with a remote endpoint. Named here: Everything (reference), Filesystem (reference), Time (reference). VS Code reads MCP servers from mcp.json, using either a mcpServers object or a servers object. Those shapes are quoted on the VS Code hub from the VS Code docs. The VS Code block on each server page is generated from that server's registry entry and can differ from the package name in the docs examples.

Category hub: Reference & Testing. The same category for Claude and Cursor.

Paid listings (Sponsored, then Featured) appear first in every list, marked Advertisement. Organic listings follow, sorted by GitHub stars. Sorted by GitHub stars as of 2026-10-17. Servers with no public GitHub repo follow, in alphabetical order.

• Everything (reference) — stdio (local, npm). Test server from the MCP maintainers that exercises prompts, resources and tools; useful for checking a client. · ★ 91,330 GitHub stars · 2026-10-17
• Filesystem (reference) — stdio (local, npm). Reference server for reading and writing local files, limited to directories you allow. · ★ 91,330 GitHub stars · 2026-10-17
• Time (reference) — stdio (local, pypi). Reference server for current time lookups and time-zone conversions. · ★ 91,330 GitHub stars · 2026-10-17