Lathe

computer.lathePublished by lathe.computerOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

Lathe is a remote MCP endpoint that gives an assistant access to managed Postgres, Redis, CouchDB and NATS instances on a dedicated EU machine.

What you can do
  • The manifest lists no tools, so the exact operations are not documented here.
  • Based on the description, it is meant to give an assistant access to managed Postgres, Redis, CouchDB and NATS running on a dedicated machine in the EU.
  • Access is through a hosted endpoint at mcp.lathe.computer, either with an API key or an OAuth sign-in.
When to use it
Worth considering when you want an assistant to work with your Lathe-hosted databases and messaging services without setting up a local server, and you are comfortable with a single flat-price managed hosting arrangement in the EU.
Requirements
A remote streamable HTTP endpoint at mcp.lathe.computer; nothing to install locally. Authentication is optional: either an Authorization header with a bearer API key taken from the portal's Account page, or OAuth sign-in, where the endpoint's 401 response names its authorization server.
Before you install
The server asks for an API key or OAuth credentials that grant access to your hosted databases and messaging services; treat the key as a secret. The service is a paid managed hosting product with one flat price, so expect billing. No tool list is published, so what the assistant can read, write or delete is not documented here.

Installation

In SourceWeft

  1. Open Lathe in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/computer.lathe%2Flathe/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lathe": {
      "type": "http",
      "url": "https://mcp.lathe.computer/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Lathe integrations