Filesystem vs Prover
A side-by-side look at the Filesystem and Prover MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Filesystem for file systems work as a local process; choose Prover for code execution over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
Choose Prover when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
lean4_build, lean4_prove_theorems, lean4_get_job_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | Code Execution |
| Quality signal | 85/100 · Excellent | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,546 | 0 |
| Directory activity | 11 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 17 | 3 |
| Full listing | View Filesystem | View Prover |
Tools & capabilities
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on the listing page
Prover tools 3
lean4_buildCompile Lean 4 source code in a Mathlib-enabled sandbox. Code is sent to external cloud services for compilation; if proving, also for AI processing.lean4_prove_theoremsAutomatically prove Lean 4 theorems that contain `sorry`. Code is sent to external cloud services for compilation and AI proving.lean4_get_job_statusPoll for the status and result of any ax-prover job.
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": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Prover
{
"mcpServers": {
"prover": {
"url": "https://prover.axiomatic-ai.com/mcp/"
}
}
}
Frequently asked questions
Filesystem is categorized under File Systems and uses a local stdio subprocess. Prover belongs to Code Execution and uses a remote HTTP/SSE transport. Pick Filesystem for file systems work and Prover for code execution.
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.
Filesystem is listed as free. Auth: no auth required. Prover has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 prover 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,546 GitHub stars. Prover has 60/100 (Good) with 0 views, 0 installs and 0 GitHub stars.