Integration

Parma CRM integration

Parma is a minimalist relationship CRM. List, search, create, update and delete relationships (people and companies with their contact details and custom field values), add them to or remove them from groups, write and edit notes linked to relationships, and read deals, pipelines, stages, groups (with their custom fields) and workspace users. Relationships, notes and users are personal data. Authentication is a personal API token from the API page of the Parma app, sent as a Bearer token; it acts with the full access of its owner's workspace.

Connect Parma CRM How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Parma CRM.Built from the 21 Parma CRM tools below, on the connection you add once.

What you can do with Parma CRM

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.

Relationship, 5 operations

create_relationshipCreate relationshipPOSTCreates a relationship, a person or a company, in one or more groups. A person can be linked to a company with company_id. Contact details cannot be set through this tool. Returns the created relationship.
delete_relationshipDelete relationshipDELETEPermanently deletes a relationship from the workspace.
get_relationshipGet relationshipGETReturns one relationship by id: name, type, about text, company, groups, contact details (email, phone, address, social handles) and custom field values. Personal data.
list_relationshipsList relationshipsGETLists or searches the relationships (people and companies) of the workspace, newest first, one page at a time, with contact details, groups and custom field values. meta.count is the total. Personal data.
update_relationshipUpdate relationshipPATCHUpdates a relationship: name, type, about text, company, groups and custom field values. Only the fields you send change. Contact details cannot be changed through this tool.

Group, 4 operations

add_relationship_to_groupAdd relationship to groupPOSTAdds a relationship to a group. Returns the membership (its id and the group_id); when the relationship is already in the group, the existing membership is returned.
list_groupsList groupsGETLists the groups (relationship lists) of the workspace, newest first, each with the custom fields it defines. Pass query to keep only groups whose name contains that text.
list_relationship_groupsList relationship groupsGETLists the groups a relationship belongs to. Each entry is a membership with its own id (used by remove_relationship_from_group) and the group_id.
remove_relationship_from_groupRemove relationship from groupDELETERemoves a relationship from a group by deleting the membership. The relationship and the group themselves are kept.

Note, 4 operations

create_noteCreate notePOSTCreates a note linked to one or more relationships. The note date defaults to now. Returns the created note with its id.
list_notesList notesGETLists the notes of the workspace, newest first, one page at a time: body, note date and the ids of the relationships each note is linked to. Note bodies may hold personal data.
list_relationship_notesList relationship notesGETLists the notes linked to one relationship, newest first, one page at a time. Note bodies may hold personal data.
update_noteUpdate notePATCHUpdates a note: its text, its date or the relationships it is linked to. Only the fields you send change.

Deal, 2 operations

get_dealGet dealGETReturns one deal by id: name, amount, status, linked relationship, pipeline and stage, owner, and creation, update and close dates.
list_dealsList dealsGETLists the deals of the workspace, newest first, one page at a time: name, amount, status, linked relationship, pipeline, stage, owner and dates. meta.count is the total number of deals.

Pipeline, 2 operations

get_pipelineGet pipelineGETReturns one deal pipeline by id: name, position, and creation and update dates.
list_pipelinesList pipelinesGETLists the deal pipelines of the workspace with their name and position.

Stage, 2 operations

get_stageGet stageGETReturns one deal stage by id: name, position, pipeline, and creation and update dates.
list_stagesList stagesGETLists the deal stages of the workspace with their name, position and pipeline.

Me, 1 operation

get_current_userGet current userGETReturns the user who owns the API token (id, name, email) and the workspace (account id and name) it acts in.

User, 1 operation

list_usersList usersGETLists the users (team members) of the workspace with their name and email address.

Use Parma CRM from Claude Code, Cursor or Codex

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

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