Runlane

run.runlanePublished by runlane.runOfficial publisherv0.1.0Updated Oct 24, 2026

Kanban board for teams and coding agents: manage tasks, subtasks, sprints and wiki pages via MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Runlane lets an assistant manage a team kanban board: tasks, subtasks, sprints and wiki pages over a remote MCP endpoint.

What you can do
Runlane is a remote kanban board for teams and coding agents, reached over streamable HTTP. Through MCP an assistant can work with tasks, subtasks, sprints and wiki pages on the board. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Worth adding when a team keeps its work on Runlane and wants an assistant to read or update board items, break work into subtasks, handle sprints, or consult wiki pages without switching apps.
Requirements
A remote endpoint at runlane.run over streamable HTTP, plus a bearer token generated in Runlane under Settings, sent in the Authorization header. No local runtime or environment variables are declared.
Before you install
The Authorization bearer token is a credential granting access to the board; keep it private and revoke it if exposed. The manifest does not list tools, so confirm what the assistant can change, such as tasks, sprints or wiki pages, before granting access.

Installation

In SourceWeft

  1. Open Runlane in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/run.runlane%2Fboard/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": {
    "runlane": {
      "type": "http",
      "url": "https://runlane.run/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

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