Integration

RogerRoger integration

RogerRoger is a sales CRM with a unified inbox (email, LinkedIn, WhatsApp) and Kanban boards for deals and tasks. Search, create and update people and organizations (personal data: names, email addresses, phone numbers, addresses), read and write their notes, manage tags and contact lists, create, update and duplicate tasks or deals on a workspace board, comment on them and read their change history. Updates are partial: only the fields sent change, and a list field sent replaces the whole list. Related records are referenced by IRI paths such as /tags/<id>. Left out: the full-replace variants of each update, sending WhatsApp messages through a connected personal account, a task export route the reference does not explain, and the routes the vendor keeps for its own web app. The API allows 20 requests per minute per account. Authentication: an API key created by an administrator in the RogerRoger admin (an active subscription is required), sent in the X-API-KEY header.

Connect RogerRoger How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with RogerRoger

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Note, 9 operations

create_organization_noteCreate organization notePOSTAgents: ask firstAdds a note to an organization. description (the text) and category (an IRI from list_note_categories) are required; title, flagged and isPrivate are optional.
create_person_noteCreate person notePOSTAgents: ask firstAdds a note to a person. description (the text) and category (an IRI from list_note_categories) are required; title, flagged and isPrivate are optional.
delete_organization_noteDelete organization noteDELETEAgents: ask firstDeletes a note from an organization (the vendor says it removes or archives the note). This cannot be undone through this API.
get_organization_noteGet organization noteGETAgents: ask firstReturns one note of an organization: title, text, category, author, flagged and private state.
get_person_noteGet person noteGETAgents: ask firstReturns one note of a person: title, text, category, author, flagged and private state.
list_organization_notesList organization notesGETAgents: ask firstLists the notes attached to an organization, in pages of up to 30. Filter by category, author, flagged state, creation date or free text.
list_person_notesList person notesGETAgents: ask firstLists the notes attached to a person (their text may hold personal data), flagged first then by creation date, in pages of up to 30. Filter by category, author, flagged state, creation date or free text.
update_organization_noteUpdate organization notePATCHAgents: ask firstUpdates a note of an organization: only the fields sent change (text, title, category, flagged, private).
update_person_noteUpdate person notePATCHAgents: ask firstUpdates a note of a person: only the fields sent change (text, title, category, flagged, private).

Comment, 4 operations

create_task_commentCreate task commentPOSTAgents: ask firstAdds a comment to a task. description (the text) is required; mentions (user IRIs) and flagged are optional.
get_task_commentGet task commentGETAgents: ask firstReturns one comment on a task: text, author, mentions, flagged state and creation date.
list_task_commentsList task commentsGETAgents: ask firstLists the comments on a task, in pages of up to 30, filtered by author, flagged state or creation date.
update_task_commentUpdate task commentPATCHAgents: ask firstUpdates a comment on a task: only the fields sent change (text, flagged, mentions).

Organization, 4 operations

create_organizationCreate organizationPOSTAgents: ask firstCreates an organization in the CRM. title (the name) is required; description, website, numbers, owner, emails, phone numbers, address, people, tags and lists are optional. Returns the new organization with its id.
get_organizationGet organizationGETAgents: ask firstReturns one organization with its description, website, registration and customer numbers, owner, people, tags, lists, email addresses, phone numbers and address.
list_organizationsList organizationsGETAgents: ask firstLists CRM organizations in pages of up to 30, filtered by free text, email, LinkedIn id or phone (identifiers[]), tag, contact list, owner, creation date or archived state. Each record's id builds its IRI /organizations/<id>.
update_organizationUpdate organizationPATCHAgents: ask firstUpdates an organization: only the fields sent change, and a list field (people, tags, lists, emails, phones) replaces the current list. Read it with get_organization first to keep existing entries.

Person, 4 operations

create_personCreate personPOSTAgents: ask firstCreates a person in the CRM (personal data). familyName is required; names, job title, owner, emails, phone numbers, address, tags, lists and organizations are optional. Returns the new person with its id.
get_personGet personGETAgents: ask firstReturns one person with names, job title, owner, tags, lists, organizations, email addresses, phone numbers and address (personal data).
list_peopleList peopleGETAgents: ask firstLists CRM people (personal data: names, emails, phone numbers, addresses) in pages of up to 30, filtered by free text, fuzzy full name, email, LinkedIn id or phone (identifiers[]), tag, contact list, owner, creation date or archived state.
update_personUpdate personPATCHAgents: ask firstUpdates a person (personal data): only the fields sent change, and a list field (tags, lists, organizations, emails, phones) replaces the current list. Read the person with get_person first to keep existing entries.

Segment, 4 operations

create_contact_listCreate contact listPOSTAgents: ask firstCreates a contact list (called a segment in the API). title and icon are required; sequence sets its order. Its IRI /segments/<id> adds people and organizations to it.
get_contact_listGet contact listGETAgents: ask firstReturns one contact list (segment): title, icon and order.
list_contact_listsList contact listsGETAgents: ask firstLists the account's contact lists (called segments in the API: title, icon, order) in pages of up to 30. A list's IRI, used on people and organizations, is /segments/<id>.
update_contact_listUpdate contact listPATCHAgents: ask firstUpdates a contact list (segment): only the fields sent change (title, icon, sequence).

Tag, 4 operations

create_tagCreate tagPOSTAgents: ask firstCreates a tag. title is required; description and background and text colours are optional. Returns the tag with its id; its IRI /tags/<id> tags people, organizations and tasks.
get_tagGet tagGETAgents: ask firstReturns one tag: title, description, background and text colour.
list_tagsList tagsGETAgents: ask firstLists the account's tags (title, colours, description) in pages of up to 30. A tag's IRI, used to tag people, organizations and tasks, is /tags/<id>.
update_tagUpdate tagPATCHAgents: ask firstUpdates a tag: only the fields sent change (title, description, background or text colour).

Task, 4 operations

create_taskCreate taskPOSTAgents: ask firstCreates a task or deal on a workspace board. title and status (the column IRI from list_workspaces) are required; assignees, tags, linked people and organizations, dates and estimates are optional.
get_taskGet taskGETAgents: ask firstReturns one task or deal: title, description, workspace and column (status), assignees, observers, tags, linked people and organizations, subtasks, dates, estimates and files.
list_tasksList tasksGETAgents: ask firstLists tasks and deals in pages of up to 30, filtered by workspace, column, assignee, author, observer, tag, linked person or organization, and by due, created, completed, scheduled or archived dates.
update_taskUpdate taskPATCHAgents: ask firstUpdates a task or deal: only the fields sent change, and a list field (assignees, observers, tags, people, organizations) replaces the current list. Set status to move it; completedAt completes it.

History, 2 operations

get_task_history_entryGet task history entryGETAgents: ask firstReturns one change history entry of a task: its author, date and list of changes.
list_task_historyList task historyGETAgents: ask firstLists the change history of a task (who changed what and when), in pages of up to 30.

Workspace, 2 operations

get_workspaceGet workspaceGETAgents: ask firstReturns one workspace (board) with its columns (id, title, position, colour, behaviour, deal probability) and its users' IRIs.
list_workspacesList workspacesGETAgents: ask firstLists the workspaces (boards) in pages of up to 30, each with its columns and users. Column ids build the status IRI /workspaces/<workspace id>/columns/<column id> that create_task needs.

Duplicate, 1 operation

duplicate_taskDuplicate taskPOSTAgents: ask firstCopies a task into a new task. Optionally set the new task's title, column (status IRI), template flag, linked people and organizations. Returns the new task.

Note category, 1 operation

list_note_categoriesList note categoriesGETAgents: ask firstLists the note categories ordered by sequence. A category's IRI, /note_categories/<id>, is required when creating a person or organization note.

Use RogerRoger from Claude Code, Cursor or Codex

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

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