Integration

Kite Suite integration

Kite Suite is a project management workspace (tasks, sprints, epics, releases, boards). Read and create projects; list, create, update, move and delete tasks and sub-tasks; plan sprints and move tasks into them; manage epics, releases, board lists, labels and task checklists; list teams and workspace users; and search a workspace. Forms, campaigns, documents, whiteboards, dashboards, automations, imports, chat and the ATS v2 API (a separate workspace key) are not exposed. Authentication is a Kite Suite API token sent in the api-token header; every tool also takes the workspace key.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Kite Suite.Built from the 40 Kite Suite tools below, on the connection you add once.

What you can do with Kite Suite

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.

Task, 9 operations

  • create_subtaskCreate subtaskPOSTCreates a sub-task under a parent task.
  • create_taskCreate taskPOSTCreates a task in a project: summary, issue type, description, assignee, sprint, labels and story points. Returns the task with its _id.
  • delete_taskDelete taskDELETEDeletes a task.
  • get_taskGet taskGETReturns one task: summary, description, issue type, priority, list, sprint, epic, assignee, reporter, labels, story points, due date, sub-tasks and linked issues.
  • list_assignee_tasksList assignee tasksGETLists the tasks assigned to a user (user ids come from list_workspace_users).
  • list_project_subtasksList project subtasksGETLists all sub-tasks of a project (tasks whose parentTask is set).
  • list_project_tasksList project tasksGETLists all tasks of a project, with their summary, type, priority, list, sprint, assignee and due date.
  • move_task_to_projectMove task to projectPOSTMoves a task to another project.
  • update_taskUpdate taskPATCHUpdates a task: summary, description, issue type, list, assignee, sprint, labels or story points. Leave a field out to keep its current value.

Sprint, 7 operations

  • complete_sprintComplete sprintPOSTCompletes a sprint; moveSprint names the sprint that receives its unfinished tasks.
  • create_sprintCreate sprintPOSTCreates a sprint in a project with a name, start and end dates, duration and goal.
  • get_sprintGet sprintGETReturns one sprint: name, start and end dates, duration in weeks, goal and task ids.
  • list_completed_sprintsList completed sprintsGETLists the completed sprints of a project.
  • list_project_sprintsList project sprintsGETLists the sprints of a project: name, start and end dates, duration in weeks, goal and task ids.
  • move_tasks_to_sprintMove tasks to sprintPOSTMoves tasks into a sprint at a given position.
  • update_sprintUpdate sprintPUTUpdates a sprint's name, dates, duration or goal.

List, 4 operations

  • create_listCreate listPOSTAdds a list (board column) to a project.
  • list_project_listsList project listsGETLists the lists (board columns, such as To do or In progress) of a project, with their order, status and task ids.
  • move_task_to_listMove task to listPATCHMoves a task to another list (board column) at a given position, for example from In progress to Done.
  • update_listUpdate listPATCHRenames a list (board column) or changes its status.

Project, 4 operations

  • create_projectCreate projectPOSTCreates a project in the workspace with a name, type, lead, description and members (emails).
  • get_projectGet projectGETReturns one project: name, key, type, privacy, lead, owner, members, lists and labels.
  • list_my_projectsList my projectsGETLists the projects of the token's user in the workspace; each entry holds a project object (_id, projectName, key, type, lead, members). Start here for project ids.
  • update_projectUpdate projectPUTUpdates a project's name, type, lead, description or favorite flag.

Release, 4 operations

  • create_releaseCreate releasePOSTCreates a release in a project with a title, description, start and release dates and a manager.
  • get_releaseGet releaseGETReturns one release: title, manager, start and release dates, status, task ids and resources.
  • list_project_releasesList project releasesGETLists the releases of a project: title, manager, start and release dates, status, task ids and resources.
  • update_releaseUpdate releasePATCHUpdates a release's title, description, dates, manager, status (for example unreleased) or resources.

Epic, 3 operations

  • create_epicCreate epicPOSTCreates an epic in a project.
  • list_project_epicsList project epicsGETLists the epics of a project: name, description, list, assignee, reporter and labels.
  • update_epicUpdate epicPATCHUpdates an epic's summary, description, assignee, reporter, labels, list or parent epic. Leave a field out to keep it.

Checklist item, 2 operations

  • create_checklist_itemCreate checklist itemPOSTAdds a checklist item to a task.
  • update_checklist_itemUpdate checklist itemPATCHRenames a checklist item or checks or unchecks it.

Team, 2 operations

  • get_teamGet teamGETReturns one team: name, description and member ids.
  • list_teamsList teamsGETLists the teams of the workspace: name, description and member ids.

User, 2 operations

  • get_userGet userGETReturns one user: full name, email, job title, department, workspaces and online status. Contains personal contact details.
  • list_workspace_usersList workspace usersGETLists the users of a workspace (id, full name, email, job title, department, status). Contains people's contact details. Takes the workspace _id from list_user_workspaces.

Workspace, 2 operations

  • list_user_workspacesList user workspacesGETLists the workspaces of a user, with each workspace's _id and name.
  • search_workspaceSearch workspaceGETSearches the workspace for tasks, epics, forms, whiteboards and documents matching a text, with optional filters by type, projects, assignees, reporters, status and priorities.

Label, 1 operation

  • create_labelCreate labelPOSTCreates a label in a project and puts it on a task.

Use Kite Suite from Claude Code, Cursor or Codex

Connect Kite Suite in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Kite Suite 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 Kite Suite

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Kite Suite once

    Add your Kite Suite connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Kite Suite integration FAQ

What can you do with the Kite Suite integration?

LiveContext exposes 40 operations on Kite Suite, covering task, sprint, list and project.

Popular integrations

Browse the whole catalog