Integration

Planview AgilePlace integration

Planview AgilePlace (formerly LeanKit) is a Kanban work management tool. Read boards, search and filter cards (by board, lane, type, assigned user, text or last update), get a card with its comments, attachments and custom fields, follow planning series and increments with card counts per status, read lane policy rules, and upload or download card images. This integration covers the routes AgilePlace publishes in its OpenAPI document; creating, updating, moving and commenting on cards, and creating or changing policy rules, are not offered here. Authentication is an API token sent as a Bearer token (create it under My API Tokens in your AgilePlace user profile) or your user name and password, on your account host (the subdomain of yourname.leankit.com).

Connect Planview AgilePlace How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Planview AgilePlace.Built from the 15 Planview AgilePlace tools below, on the connection you add once.

What you can do with Planview AgilePlace

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Image, 3 operations

download_card_imageDownload card imageGETDownloads an image attached to a card and stores it as a file.
download_imageDownload imageGETDownloads an image by its ID (for example one uploaded with upload_card_image) and stores it as a file.
upload_card_imageUpload card imagePOSTUploads an image to a board, optionally for one card, so it can be used in cards. Returns the image ID and URL.

Card, 2 operations

get_cardGet cardGETReturns one card by ID: title, description, board, lane, type, priority, size, planned and actual dates, tags, blocked status, assigned users and teams, attachments, comments, parent cards, custom fields and scoring.
list_cardsList cardsGETLists the cards the user can access, 200 per page by default, filtered by board, lanes, card IDs, text search, card types, assigned users, lane class or last update date, and sorted as asked.

Policy rule, 2 operations

get_policy_ruleGet policy ruleGETReturns one lane policy rule of a board by ID.
list_policy_rulesList policy rulesGETLists the lane policy rules of a board: the card fields each rule requires, the lanes and card types it applies to, and whether it is enabled, warns on violation or is enforced.

Series, 2 operations

get_planning_seriesGet planning seriesGETReturns one planning series by ID: label, time zone, whether all boards may use it, and its boards.
list_planning_seriesList planning seriesGETLists the planning series of the account (each a set of planning increments), 100 per page by default.

Status, 2 operations

get_increment_statusGet increment statusGETCounts the cards of a planning increment per status category (not started, in progress, completed, committed, unplanned), with the number blocked in each. Optionally only some boards.
list_increment_card_idsList increment card idsGETLists the IDs of the cards of a planning increment in one status category, and which of them are blocked. Optionally only some boards.

Board, 1 operation

list_boardsList boardsGETLists the boards the user can access, with ID, title, description and the user's board role. Filter by title, by board IDs or by minimum role; archived boards need organization administrator access.

Increment, 1 operation

list_planning_incrementsList planning incrementsGETLists the planning increments of a planning series with their labels, start and end dates and sub-increments, sorted by date.

Lane map, 1 operation

get_lane_policy_mapGet lane policy mapGETReturns, for each lane of a board, the IDs of the policy rules that apply to it.

Me, 1 operation

get_current_userGet current userGETReturns the user the credential belongs to: ID, name, email, organization, time zone, license type, administrator flag, settings (recent and favorite boards) and board roles.

Use Planview AgilePlace from Claude Code, Cursor or Codex

Connect Planview AgilePlace in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Planview AgilePlace operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Planview AgilePlace

Create your workspace
Sign up free. Nothing to install.
Connect Planview AgilePlace once
Add your Planview AgilePlace connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.