Filesystem vs StandardGraph

A side-by-side look at the Filesystem and StandardGraph MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Filesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth requiredStandardGraph logoStandardGraphEducation158,000+ K-12 education standards across 300 curriculum systems, cross-referenced via NLP.37FairAuth: no auth required

Verdict: choose Filesystem for file systems work as a local process; choose StandardGraph for education. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like path, head, tail.
Explore Filesystem

StandardGraph logoChoose StandardGraph when

  • You need dedicated capabilities in the Education domain.
  • Its auth model fits you: No auth required.
Explore StandardGraph

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFilesystem logoFilesystemStandardGraph logoStandardGraph
CategoryFile SystemsEducation
Quality signal85/100 · Excellent37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNo auth required
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars91,5125
Directory activity 11 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools17Not listed

Tools & capabilities

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on the listing page

StandardGraph tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

StandardGraph

No confirmed install command for StandardGraph yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Filesystem is categorized under File Systems and uses a local stdio subprocess. StandardGraph belongs to Education and uses an install path we have not confirmed yet. Pick Filesystem for file systems work and StandardGraph for education.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. StandardGraph has no confirmed install command yet — follow its own setup instructions.

Filesystem is listed as free. Auth: no auth required. StandardGraph has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add filesystem and standardgraph as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Filesystem has a quality signal of 85/100 (Excellent) with 11 views, 0 installs and 91,512 GitHub stars. StandardGraph has 37/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.