Integration

Peerdom integration

Peerdom maps how an organization really works: circles (groups), the roles inside them and the peers who hold those roles. List, read, create, update and delete peers, groups and roles; assign peers to roles one by one or in bulk and set their focus, time share and election date; mirror a role into other circles; manage projects, goals attached to circles, custom-field definitions, and pages built from text or image cards; and import peers, groups, roles and holders in one atomic request. Peers carry personal data (names, emails, birthdates, photos). Activating paid Peerdom apps is left out. API access needs a paid Peerdom+ plan or an active trial; authentication is an API key created in the organization's settings and sent in the X-Api-Key header.

Connect Peerdom How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Peerdom

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.

Card, 9 operations

attach_card_to_pageAttach card to pagePOSTLink an existing card to a page. `mirrored` links the same card, so edits propagate to every page that shares it; `independent` (default) clones the card first, so edits do not propagate.
create_cardCreate cardPOSTCreates a text card (type text, with text) or an image card (type image, with imageUrl, a public https image Peerdom fetches). Link it to a page afterwards with attach_card_to_page.
delete_cardDelete cardDELETEPermanently delete the card, its content, and every page link (it disappears from all pages). To remove a card from a single page without deleting it, use unlink_card_from_page.
get_cardGet cardGETFetch a card, including `pageCount` (how many pages share it).
list_cardsList cardsGETLists the organization's cards (text or image blocks that can appear on pages), optionally only those of one type or on one page.
list_page_cardsList page cardsGETList the cards on a page, in their per-page order.
reorder_page_cardsReorder page cardsPUTRewrite the order of a page's cards. Send the FULL, ordered list of the page's current card ids; each card's position becomes its array index.
unlink_card_from_pageUnlink card from pageDELETERemoves the card from this page only. The card itself, and its links to any other pages, are unaffected. To delete the card entirely use delete_card.
update_cardUpdate cardPATCHEdit a card's content. The change applies to EVERY page the card is linked to (mirrored cards share one content row). `type` may be switched between `text` and `image`.

Peer, 9 operations

assign_roleAssign rolePOSTAssigns a role to a peer, with an optional time share, focus and election end date.
create_peerCreate peerPOSTCreates a peer. With an email, a Peerdom account is found or created for that address and given a permission in your organization; no invitation email is sent.
delete_peerDelete peerDELETEDeletes a peer from the organization.
get_peerGet peerGETReturns one peer (personal data: name, email, birthdate, photo), with custom fields and held roles on request.
get_role_peerGet role peerGETReturns how a peer holds a role: time share, focus and election end date.
list_peersList peersGETLists the organization's peers (people) with names, email, birthdate and photo URL; former peers only with includeFormer. Personal data.
unassign_roleUnassign roleDELETERemoves a peer from a role they hold.
update_peerUpdate peerPUTUpdates a peer's names, email, birthdate, contribution percentage or custom-field values.
update_role_holderUpdate role holderPUTUpdates how a peer holds a role: time share in percent, focus and election end date.

Custom field definition, 5 operations

create_custom_field_definitionCreate custom field definitionPOSTCreates one custom-field definition: its name, type, the kind of record it belongs to, and its list, relation and label settings. Create it before writing its values on peers, groups, roles, projects or goals.
delete_custom_field_definitionDelete custom field definitionDELETEDelete a definition and, via cascade, every value stored against it.
get_custom_field_definitionGet custom field definitionGETFetch a single definition by id, including its `type`, `multiEntry`, `entity` and `nodeType`, so values can be verified before being written.
list_custom_field_definitionsList custom field definitionsGETList the organization's custom-field definitions (the schema/vocabulary, not the per-entity values). Call this before writing peers/roles/groups so source data maps to the organization's real field names.
update_custom_field_definitionUpdate custom field definitionPATCHUpdate side-effect-free fields of a definition: `name` (the API key used to write values by name), `translation` (display labels), `order` and `public`. A rename updates BOTH the API key and the label.

Group, 5 operations

create_groupCreate groupPOSTCreates a group (circle) on a map, inside a parent group or as an external group, with optional color, shape, goals and custom-field values.
delete_groupDelete groupDELETEDeletes a group (circle) from the live or a draft map.
get_groupGet groupGETReturns one group (circle) from the live or a draft map, with its parent, color, shape, goals and, on request, custom fields.
list_groupsList groupsGETLists the groups (circles) of the live map, or of another map with mapId; filter by peer, include custom fields with with=customfields.
update_groupUpdate groupPUTUpdates a group (circle): name, color, shape, parent, external flag, goals, group email or custom-field values.

Page, 5 operations

archive_pageArchive pageDELETEArchives a page; it is not deleted, stays readable with get_page and can be restored with update_page (archived false).
create_pageCreate pagePOSTCreates a page, a titled and ordered collection of cards; add cards to it with create_card and attach_card_to_page.
get_pageGet pageGETReturns one page with its name, description, visibility and archive state, and its cards in page order when with is cards.
list_pagesList pagesGETList the organization's pages, newest-updated first.
update_pageUpdate pagePATCHUpdate a page's name, description, visibility or archived state.

Role, 5 operations

create_roleCreate rolePOSTCreates a role inside a group (circle) of a map, or as an external role, with optional color, shape, goals, contribution target and custom-field values.
delete_roleDelete roleDELETEDeletes a role from the live or a draft map.
get_roleGet roleGETReturns one role with its parent group, color, shape, goals and mirror group, plus holders, custom fields or parent group on request.
list_rolesList rolesGETGet a list of all roles within the organization's namespace. Optionally filterable to only include roles held by a given peer or that belong to a given group. The result may optionally be extended by showing a list of peers holding the roles.
update_roleUpdate rolePUTUpdates a role: name, color, shape, parent, electable and external flags, goals, represented group, contribution target or custom-field values.

Project, 4 operations

create_projectCreate projectPOSTCreate a project for the organization. Optionally attach it to a circle (`circleId`) and/or nest it under a parent project (`parentId`). Requires the Projects app to be enabled.
get_projectGet projectGETReturns one project with its description, notes, external link, dates and archive state.
list_projectsList projectsGETGet a list of projects within the organization's namespace. Optionally filterable to only include projects that belong to a given peer.
update_projectUpdate projectPATCHPatch a project. Every field is optional; only the supplied fields are changed. Renaming regenerates the slug. Requires the Projects app.

Goal, 3 operations

create_goalCreate goalPOSTCreate a goal attached to a circle (`nodeId`). The goal `data` carries its name, order and completion (isComplete or subgoals). Requires the Goals app to be enabled.
delete_goalDelete goalDELETEDelete a goal and its circle links. Requires the Goals app.
update_goalUpdate goalPATCHPatch a goal. Every field is optional; only the supplied fields change. `nodeId` re-attaches the goal to a different circle. Requires the Goals app.

Map, 2 operations

create_draft_mapCreate draft mapPOSTCreates a draft map of the organization, private or public, next to the live map; its id can be used as mapId when creating groups and roles.
list_mapsList mapsGETLists the organization's maps (the live map and drafts) with their draft, private and archived flags and layout.

Mirror, 2 operations

list_mirrorsList mirrorsGETReturn every role sharing this role's template, the full mirror group, including the role itself. Returns an empty array when the role is standalone (not part of a mirror group).
mirror_roleMirror rolePOSTCreate mirrored copies of a role across the given target parent circles. Every copy shares the source role's template, so the whole mirror group keeps its custom fields and goals in sync, editing one propagates to all siblings.

Photo, 2 operations

remove_peer_photoRemove peer photoDELETERemove a peer's profile photo. The peer's `avatarUrl` is cleared and the stored image is retired. Returns the updated peer. Calling this on a peer with no photo is a no-op and still returns `200`.
set_peer_photoSet peer photoPOSTSet (upload or replace) a peer's profile photo. The image is resized and stored, and the peer's `avatarUrl` is updated.

Bulk, 1 operation

bulk_assign_holdersBulk assign holdersPOSTAssign peers to multiple roles in a single atomic request. The body is an array of `{roleId, holders[]}` groups; every assignment across every group is created in one transaction (all-or-none).

Import, 1 operation

import_mapImport mapPOSTCreates peers, groups, roles and role assignments together in one atomic request; items created in the same request reference each other through ref aliases.

Tenant, 1 operation

get_tenantGet tenantGETReturns the organization behind the API key: name, live map id and the color palette nodes must use when personal colors are off.

Use Peerdom from Claude Code, Cursor or Codex

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

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