Connect Lepsto MCP

Add https://mcp.lepsto.com as a remote MCP server, authorize your client, and ask it to list your products.

Prerequisites

Access to Lepsto and an active account.
An MCP client that supports remote HTTP servers and OAuth, or static bearer credentials.
For a headless client, an API key created by a signed-in user.

Step 1 — Add the server

Use the instructions for your client.

Run:

claude mcp add --transport http lepsto https://mcp.lepsto.com

In Claude Code, open /mcp, select Lepsto, and follow the authentication flow. See the Claude Code MCP documentation.

Add Lepsto as a custom remote connector using https://mcp.lepsto.com, then connect it and complete authorization. Use the Claude custom-connector instructions; availability can depend on your organization’s settings.

Add this server entry to your project’s .cursor/mcp.json, preserving any other servers already in the file:

{
  "mcpServers": {
    "lepsto": {
      "url": "https://mcp.lepsto.com"
    }
  }
}

Complete authentication when Cursor requests it. See the Cursor MCP documentation.

Add Lepsto as a custom connector for a remote MCP server with the URL https://mcp.lepsto.com, with no path after it, then sign in with OAuth. Whether you can add one depends on your ChatGPT plan and workspace settings. See the ChatGPT developer mode documentation.

For another client, use its remote HTTP server setup with the same endpoint. The MCP interface explains credentials and discovery.

Step 2 — Authorize access

With OAuth, sign in on Lepsto’s authorization page and review the requested scopes. openid identifies you; profile and email request profile information. These identity scopes do not grant a product role.

For a headless client, configure Authorization: Bearer with your API key using the client’s credential settings. The key is bound to its associated product: calls may omit the product argument and use that product, and a call naming another product is refused with no_tool_permission. Keep the value out of shared configuration files.

Step 3 — Verify it works

Ask:

List the Lepsto products I can access.

The agent calls organization_product_list. This is a user-scope operation: it requires an authenticated identity but no product_id or product permission grant. A successful response, including an empty list, confirms the connection.

To work on an existing product, name it in your request. The server keeps no selected product: the agent passes the product’s ID from that list on each product-scoped call, as product_id or, where the tool declares it, productId. Those calls also require the relevant permissions on that product.

If authentication fails, reconnect the client or replace a revoked key. If the list is empty, confirm that the account has a product grant, or create your first product.

Was this page helpful?