Release

MCP Server Support — Direct Access to Your Scrum Data from AI Assistants

v1.12.0 Has Been Released

"How's the current Sprint going?"—just ask your AI, and get an instant answer.
With MCP support, Lasimban and your AI assistant are now connected.

Lasimban now supports the MCP (Model Context Protocol) server. MCP-compatible AI clients such as Claude Desktop and Cursor can now directly access your project, sprint, PBI, and task data in Lasimban.

🤖 MCP Server Support

MCP (Model Context Protocol) is an open standard that enables AI assistants to read and write data from external tools. Through Lasimban’s MCP server, 7 tools are now available.

Read (6 Tools):

  • list_projects — List all projects
  • list_sprints — List sprints
  • list_product_backlog_items — List PBIs (with sprint filtering)
  • get_sprint_details — Get sprint details (including burn-up/burn-down chart data)
  • get_product_backlog_item — Get PBI details
  • get_task — Get task details

Write (1 Tool):

  • update_task_status — Update task status

💡 Use Cases

  • Daily Scrum prep: Ask your AI “Which PBIs have the most remaining tasks in the current sprint?” and get an instant breakdown
  • Progress check: “Summarize the sprint burn-down status” for a quick overview
  • Hands-free updates: Update task statuses directly through your AI conversation

🔑 API Key Management

An API key is required to connect to the MCP server. You can easily generate and manage keys from the settings page.

  • Secure key format with lsb_ prefix
  • Stored securely with SHA-256 hashing (plaintext shown only at generation time)
  • Up to 3 keys per user
  • Revoke unused keys with one click

⚙️ Setup

  1. Generate an API key from Lasimban’s settings page
  2. Add the endpoint and API key to your MCP client’s configuration
{
  "mcpServers": {
    "lasimban": {
      "url": "https://api.lasimban.team/mcp",
      "headers": {
        "Authorization": "Bearer ${LASIMBAN_API_KEY}"
      }
    }
  }
}

🧭 Technical Specifications

  • Protocol: Stateless Streamable HTTP (POST /mcp)
  • Authentication: API key (Authorization: Bearer header)
  • Response format: Markdown (LLM-friendly)
  • Infrastructure: Fully compatible with Cloud Run (no SSE, no session management)

📮 Contact Us

If you have any questions or feedback, please don’t hesitate to reach out.

Back to News