Lathe

live.lathePublished by lathe.liveOfficial publisherv1.0.1Updated Nov 2, 2026

Postgres, Redis, CouchDB, NATS, your app and its sign-in on one dedicated machine, one flat price.

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

Lathe is a remote MCP endpoint for a dedicated machine running Postgres, Redis, CouchDB, NATS, your app and its sign-in, at one flat price.

What you can do
  • The manifest lists no tools, so the exact operations are not documented here.
  • From the description, the server fronts a dedicated machine that hosts Postgres, Redis, CouchDB, NATS, an application and its sign-in.
  • An assistant connecting to it would work against that hosted stack rather than a local install.
When to use it
Worth considering if you want an assistant to work with a hosted backend stack (databases, messaging, app and auth) on one dedicated machine instead of setting up services yourself. The lack of a published tool list makes it hard to judge fit in advance.
Requirements
Remote streamable HTTP endpoint at mcp.lathe.live; no local package. Authentication is required: either an OAuth sign-in or an Authorization header carrying a bearer API key from the provider's portal Access page. A paid plan is implied by the flat-price offering.
Before you install
The endpoint requires credentials: an Authorization header with a bearer API key, or OAuth. The service is described as a paid, flat-price offering, so expect billing. Tools are not listed, so what the assistant can read, write or delete on the hosted databases and app is unknown; confirm before connecting.

Installation

In SourceWeft

  1. Open Lathe in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/live.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. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 3, 2026
  2. v1.0.0Sep 16, 2026

Score

56% 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
  • 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.