The Leanmote MCP connector lets you ask Claude questions about your Leanmote data in plain language — "how did the Platform team's DORA metrics move last quarter?" — and get answers built from live metrics, without opening a dashboard. MCP (Model Context Protocol) is the open standard Claude uses to talk to external systems.

The connector is read-only and scoped to your own organization: it can query the same data you can already see in the product, and nothing else.

Before you start

An active Leanmote account. You connect as yourself — there is no shared or service credential.
A Claude account with connectors enabled. The connector works from any Claude surface that shares your claude.ai account connectors (web, desktop, and mobile).
Your organization's integrations already synced at least once, so there is data to query.

Connect Leanmote to Claude

There are two ways to add the connector. Either way you sign in with your own Leanmote account and your own permissions apply — the connector never shares one credential between people.

Add it for yourself

In Claude, open Settings → Connectors and choose Add custom connector.
Enter the server URL: https://mcp.leanmote.com
Click Connect. Claude sends you to the Leanmote sign-in page.
Sign in with your usual Leanmote account, then review the consent screen and choose Allow access.
You land back in Claude with the connector enabled. Start a new chat and ask a question about your metrics.

Steps 1 and 2 — Claude's Add custom connector dialog. Only the name and the server URL are required; leave the OAuth fields empty.

Claude's Add custom connector dialog, showing the Name field, the Remote MCP server URL field, the optional OAuth client fields, and the Individual sign-in toggle.

Step 3 — the connector page before connecting, with the Leanmote server URL and the Connect button.

The Leanmote connector page in Claude's settings, showing <a href="https://mcp.leanmote.com" rel="nofollow noopener noreferrer" target="_blank">https://mcp.leanmote.com</a>, the message You are not connected to Leanmote yet, and a Connect button.

Step 4 — Leanmote's authorization screen. It spells out what Claude will be able to read before you allow anything.

Leanmote's Authorize Claude screen, explaining that Claude will be able to query metrics and list teams and users limited to your organization, with Allow access and Deny buttons.

Add it once for the whole team

A Claude workspace admin can add the connector for everyone from Claude's organization connector settings, using the same URL, with Individual sign-in enabled. Teammates then skip steps 1 and 2 — the connector is already listed in their Claude, and the first time they use it they sign in to Leanmote and allow access, exactly as in steps 3 to 5.

There is no token to copy or paste. Allowing access issues a per-user credential automatically, tied to the account you signed in with.

What Claude can do once connected

The connector exposes 17 tools. Claude picks the right ones on its own — you do not need to name them — but here is the full surface.

Discovery — what exists in your organization

list_available_metrics — every metric set the connector can fetch.
list_dashboards — the product dashboards and which metric sets compose them.
list_boards — your project-management boards (Jira, Linear, Azure Boards, ClickUp, Monday.com, Notion).
list_repositories — your git repositories (GitHub, GitLab, Bitbucket, Azure Repos).
list_custom_filters — the custom fields and columns available as filters.
get_data_freshness — when your data was last synced.

Metrics

get_metrics — fetch a metric set for a date range, optionally filtered by team, board, repository, or user.
list_configured_targets — the Strategic Overview targets your organization has configured.

People and teams

current_user — who you are and what your permissions allow.
list_teams and find_team_by_name — resolve team names to ids.
list_users and find_user_by_name — resolve people names to ids.

Four additional tools prefixed with staff_ are reserved for Leanmote staff supporting your account. They return an error for customer accounts.

Metric sets you can query

dora — lead time, deployment frequency, change failure rate, MTTR.
flow — WIP, throughput, cycle time, waiting time, flow efficiency.
team_activity — active days, reviews count, per-member activity.
team_collaboration — review interactions, meetings, task collaboration.
ai_tools_usage — AI tool adoption: active users, prompts, tokens, model breakdown.
ai_tools_impact — AI vs non-AI cycle time, merge rate, rework, AI lines of code.
ai_tools_roi — AI tool ROI summary. Owners and admins only.
project_financials — cost allocation per project and team. Owners and admins only.
strategic_overview — goals and quarter-over-quarter progress against configured targets. Owners and admins only.
all — the aggregated dashboard payload (flow, DORA, review collaboration, meetings, AI impact) in one call.

Example questions to ask

"Using Leanmote, compare the Platform team's DORA metrics for this quarter against last quarter and tell me which one regressed."
"What was our cycle time and throughput last month, broken down by team?"
"How many people used AI tools last week, and how does their cycle time compare to everyone else's?"
"Which repositories had the most rework in the last 30 days?"
"Is my Leanmote data up to date? When did it last sync?"

Mentioning "Leanmote" in the question helps Claude reach for the connector instead of answering from general knowledge.

Permissions, privacy, and auditing

Read-only. The connector cannot change settings, edit dashboards, or write any data back into Leanmote.
Your permissions apply. Organization scoping is enforced by Leanmote's APIs, not by Claude. You see exactly what your role already lets you see; restricted metric sets return an error for team leaders and individual contributors.
Every call is logged. Each tool invocation is recorded with the caller, the tool, the shape of the arguments, and the outcome, as part of our SOC 2 access-logging controls.
Revocation is checked per request. Your credential is validated against Leanmote on every call, so removing access takes effect within about a minute.

Rate limits

Limits are generous for interactive use and exist to protect shared infrastructure. Each call consumes "cost units": discovery calls are free, a normal get_metrics call costs 3, and requesting the aggregated all set costs 8.

Per user: 60 units per minute, 1,000 units per hour.
Per organization: 600 units per minute, 10,000 units per hour.

If you hit a limit, Claude reports how long to wait. In practice that means roughly 20 metric queries a minute per person.

Disconnect

Remove the connector from Settings → Connectors in Claude. To cut access for a teammate who has left, an organization admin can revoke their Leanmote access as usual — the connector stops working on the next call.

Troubleshooting

The connection is rejected before the login page. Only Claude's own connector callbacks are allow-listed. Connecting from a different MCP client (a CLI, an IDE plugin, or a custom script) is not enabled — contact Leanmote support if you need one added.
You are asked to log in to Leanmote. That is expected: the consent step runs on Leanmote, not in Claude. After approving, you return to Claude automatically.
Claude reports a permissions error. Cost, ROI, and Strategic Overview data is restricted to organization owners and admins.
Numbers look stale. Ask Claude when the data was last synced; the connector reads the same synced data as the dashboards, so a lagging integration shows up in both.
Claude answers without using Leanmote. Say "using Leanmote" in the question, or check that the connector is toggled on for the chat.

Working with the Leanmote API
Dashboards overview
Claude Code integration (OTLP)
Roles and access levels

Leanmote MCP connector for Claude