Integration

Infinity integration

Infinity (startinfinity.com) is a flexible work management tool built from workspaces, boards, folders, views and items whose fields are board-defined attributes. Read your profile and workspaces; list, create and update boards, attributes, folders, views and items; comment on items; attach files from a URL; link items with references; log time entries; manage board webhooks; and invite, add or remove workspace members. Authentication is a personal access token (created under Profile, Developer, Tokens) sent as a Bearer token; every call also carries the API version header, set automatically.

Connect Infinity How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Infinity.Built from the 45 Infinity tools below, on the connection you add once.

What you can do with Infinity

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.

Attribute, 5 operations

create_attributeCreate attributePOSTCreates an attribute (field) on a board. To show it in a folder, then add its id to the folder's attribute_ids with update_folder.
delete_attributeDelete attributeDELETEDeletes an attribute (field) from a board.
get_attributeGet attributeGETReturns one attribute (field) of a board: name, type, default value, settings, creator and creation date.
list_attributesList attributesGETLists the attributes (fields, such as Name, Status or Due date) of a board, with their type, default value and settings. Item values reference these ids.
update_attributeUpdate attributePUTUpdates an attribute (field). The vendor docs list name, type, default_data and settings as required here: send the current values of those you do not change (get_attribute).

Comment, 5 operations

create_commentCreate commentPOSTAdds a comment to an item, optionally as a reply to another comment. Visible to everyone with access to the board.
delete_commentDelete commentDELETEDeletes a comment from an item.
get_commentGet commentGETReturns one comment of an item. Set expand[] to created_by to include the author.
list_commentsList commentsGETLists the comments on an item (text in HTML, parent comment id for replies, date). Set expand[] to created_by to include the author.
update_commentUpdate commentPUTChanges the text of a comment.

Folder, 5 operations

create_folderCreate folderPOSTCreates a folder in a board, at the top level or inside parent_id. attribute_ids lists the fields shown in it.
delete_folderDelete folderDELETEDeletes a folder from a board.
get_folderGet folderGETReturns one folder of a board: name, color, parent, sort order, settings and the attribute ids shown in it.
list_foldersList foldersGETLists the folders of a board (name, color, parent folder, the attribute ids shown in it). Items live in folders.
update_folderUpdate folderPUTUpdates a folder; name is required by the vendor. Send attribute_ids to change which fields the folder shows (for example after create_attribute).

Item, 5 operations

create_itemCreate itemPOSTCreates an item in a board folder with its field values (attribute ids from list_attributes).
delete_itemDelete itemDELETEDeletes an item from a board.
get_itemGet itemGETReturns one item. Set expand[] to values (or values.attribute, folder, created_by) to include its field values.
list_itemsList itemsGETLists the items (rows, cards) of a board, 1 to 100 per page; pass after for the next page. Set expand[] to values to get each item's field values, folder_id to keep one folder.
update_itemUpdate itemPUTUpdates an item: its field values, its folder or its parent. Leave a field out to keep its current value.

View, 5 operations

create_viewCreate viewPOSTCreates a view (tab) in a folder, for example a list or table view.
delete_viewDelete viewDELETEDeletes a view (tab) from a folder.
get_viewGet viewGETReturns one view (tab) of a board: folder, name, type, sort order and settings.
list_viewsList viewsGETLists the views (tabs such as table, list, columns or calendar) of a board; folder_id keeps the views of one folder.
update_viewUpdate viewPUTUpdates a view's type or position; type is required by the vendor (send the current one to keep it).

Hook, 4 operations

create_hookCreate hookPOSTCreates a webhook: Infinity calls url when one of the chosen events happens on the board.
delete_hookDelete hookDELETEDeletes a webhook of the token's user.
list_hooksList hooksGETLists the webhooks the token's user has on a board: id, URL and subscribed events. Set expand[] to logs to include delivery logs.
update_hookUpdate hookPUTChanges a webhook's URL and events; both are required by the vendor.

Member, 4 operations

add_memberAdd memberPUTAdds an existing Infinity user to the workspace with a role, or changes their role.
invite_memberInvite memberPOSTSends an invitation email to join the workspace. The invite is sent at once and cannot be unsent here.
list_membersList membersGETLists the members of a workspace: id, name, email, photo, job, location and role. Contains people's contact details.
remove_memberRemove memberDELETERemoves a member from the workspace; they lose access to its boards.

Board, 3 operations

create_boardCreate boardPOSTCreates a board in a workspace. The current user is given access automatically; user_ids grants access to other workspace members.
get_boardGet boardGETReturns one board: name, color, description, sort order and the ids of the members who have access.
list_boardsList boardsGETLists the boards of a workspace: id, name, color, description and the ids of the members who have access.

Time entry, 3 operations

create_time_entryCreate time entryPOSTLogs a time entry on an item's time tracking attribute: start and end times and a description.
delete_time_entryDelete time entryDELETEDeletes a time entry of the token's user.
update_time_entryUpdate time entryPUTChanges the start, end or description of a time entry; its item and attribute cannot be changed.

Attachment, 2 operations

create_attachment_from_urlCreate attachment from urlPOSTDownloads a file from a public URL, stores it in the workspace and returns an attachment object (id, link, name, size).
upload_attachmentUpload attachmentPOSTUploads a file to the workspace and returns an attachment object (id, link, name, size). Use its id in an attachments field value.

Reference, 2 operations

create_referenceCreate referencePOSTLinks two items through a links attribute (from one item to another).
delete_referenceDelete referenceDELETERemoves a link between two items.

Profile, 1 operation

get_my_profileGet my profileGETReturns the profile of the user who owns the token: id, name, email, photo URL, job, location, tagline, role and creation date.

Workspace, 1 operation

list_workspacesList workspacesGETLists the workspaces the token's user belongs to (id, name, photo). Start here: every other tool needs a workspace id.

Use Infinity from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Infinity once
Add your Infinity 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.