# AtpMcp

> AtpMcp is an open-source MCP server for developer tools. Run theorem provers and read SZS verdicts from an agent via SystemOnTPTP and Isabelle. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, self-hosted, Linux, macOS, Windows
- **Repository:** https://github.com/jcschuster/atpmcp
- **MCP Registry name:** io.github.jcschuster/atp_mcp
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

AtpMcp wraps the AtpClient library's four theorem-prover backends: SystemOnTPTP, StarExec, Isabelle and LocalExec. An agent submits a TPTP problem and gets back a verdict in the SZS ontology, such as Theorem, Satisfiable, GaveUp or Timeout, and can call a reference tool to learn what each verdict means.

The default Docker image bundles the server, Erlang and the E prover, so SystemOnTPTP and a local E work with no setup. A larger tag adds Isabelle/HOL, which needs a few GB of RAM and about a minute to start on first use. StarExec has no defaults and needs a URL, username and password. Settings live in an atp_mcp.exs file, and an atp_mcp doctor command reports each backend's resolved settings and reachability.

The server speaks only MCP revision 2026-07-28 over stdio; clients that need the older initialize handshake are rejected. It can also be installed as an Elixir escript.

## Features

- **Four prover backends:** SystemOnTPTP, StarExec, Isabelle and local executables behind one interface.
- **SZS verdicts:** Results use the standard SZS vocabulary, with an optional raw output mode.
- **Docker images:** One image with E included, another with Isabelle/HOL.
- **Doctor command:** Prints resolved settings and reachability for each backend.
- **File-based config:** Configure defaults such as prover and time limit in atp_mcp.exs.
- **SZS reference:** A tool that explains every success and no-success status.

## Good for

- Ask an agent to prove a TPTP conjecture with a chosen prover
- Compare verdicts from several SystemOnTPTP systems
- Run a local E prover on a problem file
- Check an Isabelle problem from an editor
- Check that provers are reachable before a session

## Install

### Claude Code (Terminal)

```sh
claude mcp add atp_mcp -- docker run -i --rm ghcr.io/jcschuster/atp_mcp:0.8.1
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "atp_mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/jcschuster/atp_mcp:0.8.1"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "atp_mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/jcschuster/atp_mcp:0.8.1"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "atp_mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/jcschuster/atp_mcp:0.8.1"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "atp_mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/jcschuster/atp_mcp:0.8.1"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "atp_mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/jcschuster/atp_mcp:0.8.1"
      ]
    }
  }
}
```

## Tools

- `list_backends`: List the available prover backends
- `describe_szs`: Reference text for the SZS ontology
- `verify_backend`: Probe a backend's configuration and reachability
- `query_backend`: Submit a TPTP problem to any backend and return an SZS verdict
- `list_provers`: List provers available on SystemOnTPTP
- `run_prover`: Run a TPTP problem on a specific prover

## FAQ

### What do I need to run it?

Docker is enough with the bundled image; otherwise install the escript with Elixir 1.20 and OTP 29.

### Does Isabelle work out of the box?

Use the isabelle image tag; the server starts Isabelle on first use, which can take up to a minute.

### What protocol revision is supported?

Only MCP revision 2026-07-28 over stdio.

### How do I check my setup?

Run atp_mcp doctor.

### Is AtpMcp free?

Yes. AtpMcp is open source, so you can use and self-host it for free.

### How do I add AtpMcp to Claude Code?

Run this command in your terminal: claude mcp add atp_mcp -- docker run -i --rm ghcr.io/jcschuster/atp_mcp:0.8.1

### What are the best alternatives to AtpMcp?

The closest alternatives to AtpMcp are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

## Where this comes from

- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Context7](https://ai-powered.com/mcp/context7): Context7 is a freemium MCP server for developer tools.
- [Chrome DevTools MCP](https://ai-powered.com/mcp/chrome-devtools-mcp-2): Chrome DevTools MCP is an open-source MCP server for browser automation.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [awesome-mcp-servers](https://ai-powered.com/mcp/awesome-mcp-servers-2): awesome-mcp-servers is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.

---
Source: https://ai-powered.com/mcp/atpmcp
