Leafwright MCP server

Which servers in the official MCP registry are Leafwright's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to Leafwright

Whose server it is

Registry nameco.leafwright/leafwrightverified in the MCP registry

The registry name sits under leafwright.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-12

Stateanswerschecked 2026-10-12
Tools3
Server calls itselfleafwright
Server version0.2.4
Protocol version2025-06-18

On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 98 ms.

Tools it offers3 tools · read 2026-10-12

leafwright_login
Start a browser login flow for Leafwright MCP. Open the returned URL, choose an organization and project, then call leafwright_auth_status.
leafwright_auth_status
Check whether Leafwright MCP is authenticated. Completes a pending browser login if approved. Pass the device_code returned by leafwright_login when the client has no local storage, which is the case over HTTP.
leafwright_logout
Revoke the stored Leafwright MCP token and clear local auth state.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "leafwright": {
      "type": "http",
      "url": "https://leafwright.co/mcp"
    }
  }
}

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.