Code Runner vs Filesystem

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

Code Runner logoCode RunnerCode Execution · Local subprocess (stdio)Code Runner MCP Server which can run code in various programming languages.43FairAuth: not declaredFilesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth required

Verdict: choose Code Runner for code execution work as a local process; 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?

Code Runner logoChoose Code Runner when

  • You need dedicated capabilities in the Code Execution domain.
  • You prefer a local stdio subprocess transport.
Explore Code Runner

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.

SpecCode Runner logoCode RunnerFilesystem logoFilesystem
CategoryCode ExecutionFile Systems
Quality signal43/100 · Fair85/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars24291,546
Directory activity 2 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
ToolsNot listed17

Tools & capabilities

Code Runner 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.

Code Runner

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "code-runner": {
      "command": "npx",
      "args": [
        "-y",
        "issue"
      ]
    }
  }
}

Filesystem

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

Frequently asked questions

Code Runner is categorized under Code Execution and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Code Runner for code execution 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.

Code Runner has no declared pricing — check the project's own site. 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 code-runner and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Code Runner has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 242 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,546 GitHub stars.