StandardGraph vs Filesystem

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

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

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

Which MCP server should you choose?

StandardGraph logoChoose StandardGraph when

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

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecStandardGraph logoStandardGraphFilesystem logoFilesystem
CategoryEducationFile Systems
Quality signal37/100 · Fair85/100 · Excellent
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars591,512
Directory activity 0 views 0 installs 0 upvotes 10 views 0 installs 0 upvotes
ToolsNot listed17

Tools & capabilities

StandardGraph tools

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

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on 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.

StandardGraph

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

Filesystem

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

Frequently asked questions

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

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.

StandardGraph has no declared pricing — check the project's own site. Auth: no auth required. Filesystem is listed as free. 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 standardgraph and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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