Lathe MCP Server

by lathe Your server? Claim it

answering

Lathe is answering right now. Last checked 14 min ago.

Managed Postgres, Redis, CouchDB and NATS on a dedicated EU machine, one flat price.

Uptime history 9 days of history

9 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

261 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Lathe every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add lathe --transport http https://mcp.lathe.live

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "lathe": {
      "url": "https://mcp.lathe.live"
    }
  }
}

~/.codex/config.toml

[mcp_servers.lathe]
url = "https://mcp.lathe.live"

.cursor/mcp.json

{
  "mcpServers": {
    "lathe": {
      "url": "https://mcp.lathe.live"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "lathe": {
      "url": "https://mcp.lathe.live"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.lathe.live	streamable-http	sign-in	443 ms	14 min ago

Alternatives to Lathe

same job, measured the same way

Sota

by sota

EU-native PaaS for AI agents — deploy web apps with one sentence, managed Postgres, GDPR by default.

57 installs/wk 14 tools answering

nlqdb — analytical memory for AI agents

by nlqdb

Analytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.

answering

Tenantsdb

by tenantsdb

Multi-tenant database orchestration: isolated Postgres, MySQL, MongoDB, Redis tenants on demand.

answering

Neon

by neon

Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.

answering

Quarry

by wangggym

Safety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default.

166 installs/wk local only

Myco Brain

by thegoodguysla

Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres.

66 installs/wk local only

Postgres Redis Compose Generator

by getvda

Postgres + Redis Compose Generator

2 tools answering

Postgres MCP

by edelciomolina

PostgreSQL MCP wrapper with .env credential mapping, tool selection, and safe read-only defaults.

92 installs/wk local only

Lathe — questions

Answers built from our own checks of this server.

Why is there no tool list for Lathe?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Lathe working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 261 ms. The bar chart above shows every period we have measured.

How do I connect Lathe?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Lathe?

No API key is involved. Lathe answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Lathe?

It answers our handshake in 261 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.