Leantime MCP Bridge

Provides a robust MCP proxy bridge that connects MCP clients to Leantime servers with multiple authentication methods and SSE transport.

typescript

6

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "leantime-leantime-mcp": {
      "command": "leantime-mcp",
      "args": [
        "https://yourworkspace.leantime.io/mcp",
        "--token",
        "YOUR_TOKEN_HERE"
      ],
      "env": {
        "NODE_ENV": "production"
      }
    }
  }
}

You run a Leantime MCP Bridge to connect MCP clients with your Leantime server. It’s a TypeScript-based proxy that handles authentication, protocol negotiation, and transport so you can interact with Leantime data and actions through the MCP stack with reliability and security.

How to use

You can connect an MCP client to your Leantime instance by running the bridge locally or using a remote MCP URL. The bridge accepts a token for authentication and exposes the MCP interface to your client. Use the HTTP/HTTPS URL of your Leantime MCP endpoint or run the bridge as a local process and pass the endpoint URL and token as arguments.

Available tools

Protocol handling

Manages JSON-RPC messages using the official MCP SDK for robust protocol communication.

Authentication

Applies the selected authentication method and headers to all MCP requests.

Transport layer

Supports HTTP(S), Server-Sent Events (SSE), and streaming responses for MCP communication.

Retry logic

Implements exponential backoff with jitter to handle transient failures.

Caching

Smart caching for tool lists and prompts to reduce server load.

Session management

Tracks MCP session IDs for stateful interactions.