What is the key difference between Workspace Tools and Prover?

Workspace Tools belongs to the Code Execution category with local stdio execution, while Prover belongs to the Code Execution category with cloud HTTP/SSE execution.

How do I install Workspace Tools or Prover in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Workspace Tools and Prover free or paid?

Workspace Tools operates under a Free / Open Source model (No auth required). Prover operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Workspace Tools lists 0 tools with 0 views and 0 GitHub stars. Prover lists 3 tools with 0 views and 0 GitHub stars.

Can I use both Workspace Tools and Prover together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Workspace Tools or Prover in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Workspace Tools and Prover free to use, or do they require API keys?

Workspace Tools is listed under a Free / Open Source model with No auth required . Prover operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Workspace Tools and Prover at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both workspace-tools and prover as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Workspace Tools has a Quality Score of 32 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Prover holds a Quality Score of 48 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Workspace Tools vs Prover

In-depth architectural comparison of the Workspace Tools and Prover MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Workspace Tools

Code Execution · Local stdio

Quality: 32/100 (Emerging) | Auth: No auth required

Prover

Code Execution · Remote HTTP/SSE

Quality: 48/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Workspace Tools if you need specialized Code Execution tools running via a local process. Choose Prover if your workspace requires Code Execution integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Workspace Tools when:

You need dedicated capabilities in the Code Execution domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Workspace Tools Details

Choose Prover when:

You need dedicated capabilities in the Code Execution domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: lean4_build, lean4_prove_theorems, lean4_get_job_status.

Explore Prover Details

Feature & Specification Comparison

Specification	W Workspace Tools Code Execution	Prover Code Execution
Summary	Sandbox workspace tools: search, file read, DB queries, integrations. Returns synthetic data.	Lean 4 MCP server: compile, prove theorems, and formalize math with Mathlib.
Category & Scope	Code Execution	Code Execution
Quality signal

Tools & Capabilities Breakdown

Workspace Tools Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Prover Tools (3)

lean4_build

Compile 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_theorems

Automatically prove Lean 4 theorems that contain `sorry`. Code is sent to external cloud services for compilation and AI proving.

lean4_get_job_status

Poll for the status and result of any ax-prover job.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Workspace Tools Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "workspace-tools": {
      "command": "npx",
      "args": [
        "-y",
        "workspace-tools"
      ]
    }
  }
}

Prover Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "prover": {
      "url": "https://prover.axiomatic-ai.com/mcp/"
    }
  }
}

Frequently Asked Questions

Workspace Tools is categorized under Code Execution and uses a local stdio subprocess. In contrast, Prover belongs to Code Execution using remote streaming HTTP/SSE transport. Select Workspace Tools when you need capabilities focused on code execution and Prover when you require tools for code execution.

More alternatives to Workspace Tools More alternatives to Prover Code Execution category hub Canonical compare URL