Modjo AI MCP integration for AI agents.
Connect AI agents to Modjo AI through 20 structured actions, including get account, get call, and get call next steps. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 20
- 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 Modjo AI integration exposes
The Modjo AI Agent App exposes 20 provider-backed actions for communication, ai, and data work. Its current contract lets an authorized agent get one modjo account by id, get one modjo call by integer id or uuid with optional relation expansion, and get ai-extracted next steps for a modjo call. 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 Modjo AI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Modjo AI capabilities.
Showing 12 of 20 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADGet one Modjo account by ID.
INPUTS: id
get_callREADGet one Modjo call by integer ID or UUID with optional relation expansion.
INPUTS: id / expand
get_call_next_stepsREADGet AI-extracted next steps for a Modjo call.
INPUTS: id
get_call_transcriptREADGet the transcript for a Modjo call by integer ID or UUID.
INPUTS: id
get_contactREADGet one Modjo contact by ID.
INPUTS: id
get_deal_summaryREADGet the AI-generated summary for a Modjo deal.
INPUTS: id
get_teamREADGet one Modjo team by ID.
INPUTS: id
get_userREADGet one Modjo user by ID.
INPUTS: id
list_accountsREADList Modjo accounts with optional pagination and name filtering.
INPUTS: page / size / name
list_call_notesREADList published notes for a Modjo call.
INPUTS: id
list_call_summariesREADList AI-generated summaries for a Modjo call.
INPUTS: id
list_call_tagsREADList tags associated with a Modjo call.
INPUTS: id
INPUT CONTRACTS
Know what the action needs before it runs.
get_account
idREQUIRED- The Modjo resource ID.
get_call
idREQUIRED- The Modjo call ID. Modjo accepts a positive integer ID or UUID.
expandOPTIONAL- Relations to expand inline in a Modjo call response.
get_call_next_steps
idREQUIRED- The Modjo call ID. Modjo accepts a positive integer ID or UUID.
get_call_transcript
idREQUIRED- The Modjo call ID. Modjo accepts a positive integer ID or UUID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Get one Modjo account by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountVerify with Get Call
Get one Modjo call by integer ID or UUID with optional relation expansion. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_callSAFETY BOUNDARY
Operate Modjo AI with explicit limits
- Authorize Modjo AI with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Modjo AI data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Modjo AI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Modjo AI task completed successfully.
CONNECTION MODEL
API key
Modjo API key sent as a Bearer token in the Authorization header. Create an API key from Modjo settings as described in the Public API docs: https://api.modjo.ai/v2/docs.
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
- 20
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- 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 Modjo AI.