Parma MCP integration for AI agents.
Connect AI agents to Parma through 22 structured actions, including get current user, add relationship to group, and delete relationship. Review authenticati…
- ACTION CONTRACTS
- 22
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Parma integration exposes
The Parma Agent App exposes 22 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get the current parma user and workspace account, add a parma relationship to a group, and delete a parma relationship by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Parma account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Parma capabilities.
Showing 12 of 22 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADGet the current Parma user and workspace account.
add_relationship_to_groupWRITEAdd a Parma relationship to a group.
INPUTS: relationship_id / group_id
delete_relationshipHIGH IMPACTDelete a Parma relationship by ID.
INPUTS: id
create_noteWRITECreate a note linked to one or more Parma relationships.
INPUTS: datetime / relationship_ids / body
create_relationshipWRITECreate a person or company relationship in Parma.
INPUTS: name / type / company_id / group_ids / about
get_dealREADGet a Parma deal by ID.
INPUTS: id
get_pipelineREADGet a Parma pipeline by ID.
INPUTS: id
get_relationshipREADGet a Parma relationship by ID.
INPUTS: id
get_stageREADGet a Parma pipeline stage by ID.
INPUTS: id
get_userREADGet a Parma user by ID.
INPUTS: id
list_dealsREADList deals in the connected Parma workspace.
INPUTS: page
list_groupsREADList Parma relationship groups, optionally filtered by name.
INPUTS: query
INPUT CONTRACTS
Know what the action needs before it runs.
add_relationship_to_group
relationship_idOPTIONAL- The Parma relationship ID.
group_idOPTIONAL- The Parma group ID to assign.
delete_relationship
idOPTIONAL- The Parma resource ID.
create_note
datetimeOPTIONAL- The note date and time value accepted by Parma.
relationship_idsREQUIRED- The Parma relationship IDs linked to the note.
bodyREQUIRED- The note body text.
create_relationship
nameREQUIRED- The relationship name.
typeOPTIONAL- The relationship type.
company_idOPTIONAL- The Parma company relationship ID linked to this person.
group_idsREQUIRED- The Parma group IDs assigned to the relationship.
aboutOPTIONAL- The relationship description or notes.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Get the current Parma user and workspace account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Add Relationship To Group
Add a Parma relationship to a group. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_relationship_to_groupVerify with Get Deal
Get a Parma deal by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_dealSAFETY BOUNDARY
Operate Parma with explicit limits
- Authorize Parma with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_relationship` and `remove_relationship_from_group` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Parma rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Parma task completed successfully.
CONNECTION MODEL
API key
Parma workspace API token. Copy or create one at https://app.parma.ai/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 15
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Parma.