The Modjo Model Context Protocol (MCP) server lets your AI assistant — Claude, ChatGPT, Cursor, Dust, n8n, and any other MCP-compatible client — read and analyze your Modjo workspace data: calls, deals, accounts, contacts, transcripts, and AI agents. You ask in plain language, Modjo answers from your actual data.

Feel free to check our clients use cases of Modjo's MCP to get inspiration.

How to connect to Modjo MCP
MCP tools: what changes with V2
Using Modjo agents through the MCP
Other relevant information (best practices, limits, troubleshooting)

How to connect to Modjo MCP?

We support two authentication methods. The choice matters for security and team rollout, so read this before you start.

OAuth 2.0 (recommended, use this by default)

Each user signs in with their own Modjo account.

Use OAuth for the entire team, including managers and admins, in 99% of cases.

Bearer token via HTTP header (admin / power-user only)

A workspace API key passed as an Authorization header. The token is organization-scoped — whoever holds it can read every call, every deal, and every account across the workspace, regardless of their role in Modjo.

This is the right tool when you genuinely need workspace-wide reach: building n8n pipelines, programmatic automations, or scripts owned by an admin. It is the wrong tool for individual reps. If a rep can use OAuth, they should.

	OAuth	Bearer token
Who it's for	All users — reps, CSMs, managers	Admins, ops, automation owners
Setup	Click "Connect", sign in	Generate API key, paste header
Best for	Daily use in Claude, ChatGPT, Cursor	n8n workflows, scripts, server-side jobs
Security	Respects the activity access rules configured in Modjo	No activity access restriction applies
Token rotation	Automatic	Manual

Quick start with OAuth (recommended)

Connect Modjo to your workspace

For Claude and Dust, Modjo is available directly in their connector/tool directory, no custom MCP setup is required.

For other MCP-compatible clients, an admin may need to add the Modjo MCP manually using the URL provided below.

Claude (claude.ai web, Claude apps, Claude Code)

Modjo is available directly in Claude's connector directory:

Go to Customize → Connectors
Search for Modjo
Click Connect, sign in with Modjo, and approve access

The Modjo tools become available to Claude immediately. You can scope them per-project in Claude Projects.

ChatGPT

Open Settings → Connectors → New connector (requires ChatGPT Plus or higher, depending on rollout)
URL: https://api.mcp.modjo.ai/v1/mcp
Sign in with Modjo when prompted

Dust

Modjo is available directly in Dust's tool directory:

Go to Spaces → Tools → Add Tools
Search for Modjo
Select Modjo and complete the OAuth sign-in
Assign Modjo tools to agents in the Agent Builder

Other MCP-compatible clients

Any client supporting the MCP OAuth 2.0 spec (Authorization Code + PKCE with protected-resource metadata discovery) will work. Point it at https://api.mcp.modjo.ai/v1/mcp and let it handle the rest — the server publishes its OAuth metadata at the standard .well-known paths.

Connect as a user

Once the custom connector has been added to your workspace all you need to do is go to your workspace’s connectors (path depends on which client you use - see above), select Modjo and sign in! As simple as that.

Good to know: If you had already setup the Modjo MCP with the bearer token, we recommend you to switch to the Oauth method for simpler and safer usage by your whole team: with Oauth connection, each user only retrieves the calls, deals and accounts they can see in the app — the same rules apply to search, retrieval, and ask_anything_* results. Bearer token connections remain workspace-wide by design and are not restricted by these rules.

Also, don't forget to change the MCP source connected to your agents if you had already setup agents using the Modjo MCP!

Bearer token setup (admins & automations)

Use this only when OAuth isn't a fit — typically n8n workflows, scheduled scripts, server-to-server pipelines, or one-off admin queries that need workspace-wide reach.

Get your API key

Go to Settings → Integrations → Modjo API key in the Modjo app
Generate a key and store it somewhere safe — you won't see it again

Configure your client

The bearer token connection uses the same MCP URL. Send your API key in the Authorization header:

https://api.mcp.modjo.ai/v1/mcp

Pass your key as Authorization: Bearer <your-api-key>.

n8n (version 1.88.0+)

Automating analyses in n8n? We recommend using the Modjo Agents API rather than relying on MCP tools, whose catalog can evolve. Call the analysis directly with your instructions and expected response structure. See the API documentation and contact your Modjo account manager for more information.

n8n natively supports MCP since v1.88.0 — no community node, no extra install.

With an AI Agent (autonomous tool calls):

Add an AI Agent node with your LLM credentials
Add an MCP Client Tool node, connect it to the Agent's Tools input
Configure the MCP Client Tool:
- MCP Endpoint URL: https://api.mcp.modjo.ai/v1/mcp
- Authentication: Header Auth
- Header name: Authorization
- Header value: Bearer your-modjo-api-key-here
Under Tools to Include, choose All (or Selected for specific tools)

Standalone (deterministic tool calls):

Add an MCP Client node
Configure:
- Server Transport: Streamable HTTP
- MCP Endpoint URL: https://api.mcp.modjo.ai/v1/mcp
- Same Header Auth as Mode A
Select the Tool to execute from the dropdown
Map input parameters

Make / Zapier / Codex CLI / Gemini CLI / any HTTP MCP client

Same pattern everywhere:

{   "mcpServers": {     "modjo": {       "type": "http",       "url": "https://api.mcp.modjo.ai/v1/mcp",       "headers": {         "Authorization": "Bearer your-modjo-api-key-here"       }     }   } }

Security reminders for bearer tokens

Don't commit API keys to git. Use environment variables or your secrets manager.
Don't share keys between users. One key per automation or admin, rotated regularly.
A bearer key is workspace-wide. Anyone holding it can see every call, every deal, every account, including data from teams they don't normally have access to. Treat it like an admin password.
Prefer OAuth for individuals. Even admins doing daily analysis in Claude or ChatGPT should sign in with OAuth, keep the bearer token for systems, not seats.

MCP tools: what changes with V2

V1 tools remain available during the transition and will be marked deprecated. No removal date is announced here. If your prompts name these tools, use the mappings below when V2 is enabled for your workspace. The connection URL remains https://api.mcp.modjo.ai/v1/mcp.

Your goal	MCP V1	MCP V2
Find accounts	`get_accounts`: search accounts and their CRM references.	`search_accounts`: find accounts and activity indicators, with their Modjo IDs.
Find deals	`get_deals`: search deals by amount, dates, status, source or loss reason.	`search_deals`: find deals, their contacts and CRM fields. Check the filters available in V2.
Find contacts	`get_contacts`: find contacts, with their CRM ID, email, phone and job title.	`search_contacts`: find customer and prospect contacts and their linked accounts.
Find colleagues	`get_users`: search Modjo users, with their role and department.	`search_users`: find colleagues and their teams. Use `search_teams` to explore teams and their members.
Find calls	`get_calls`: search calls by deal, account, contact, date or user.	`search_activities`, with type `call`: select calls by entity, date, team, tag or topic, then read their content with `get_activity_content`.
Find and read emails	`get_emails`: search emails and retrieve their content.	`search_activities`, with type `email`, then `get_activity_content` to read their content.
Search by topic	`semantic_search_activities`: find calls or emails about a topic, such as objections or pricing.	`search_activities`, in `semantic` mode: search by topic and combine the available filters. Read selected results with `get_activity_content`.
Read a transcript	`get_transcript`: retrieve full transcripts for one or more calls, with timestamps and speakers.	`get_activity_content`, with detail level `transcript`: read transcripts using activity IDs obtained from `search_activities`. The `summary` level reads a call’s full summary.
Find available agents	`get_agents`: list built-in and custom agents.	No direct V2 replacement identified. This tool’s status during the transition still needs confirmation.

If your prompts name old tools, update them using the mappings above and check the result. To build automations, prefer the Modjo Agents API.

A topic search returns a selection of relevant conversations, without guaranteeing that it finds every conversation in scope.

Tools that keep their name

These three tools keep their name in V2: ask_anything_on_call for an AI question about a call, ask_anything_on_deal about a deal, and ask_anything_on_account about an account. See “Using Modjo agents through the MCP V2” below for examples.

Additional tools in V2

search_teams: find teams and their members.
search_tags: find call tags.
search_calendar_events: find upcoming meetings.
resolve_ids: translate contact, account and deal IDs between Modjo and your CRM.

Example: “Find last week’s onboarding calls for the BDR team, read their summaries and list the recurring objections.”

💡 If new tools do not appear, ask your admin to refresh the MCP connection in your AI tool’s settings.

Using Modjo agents through the MCP (MCP V2)

Use Modjo’s specialized agents to analyze your data with reusable instructions. Shared instructions make results easier to compare across reps and deals; AI responses can vary in content and format.

Built-in agents

Agent	UUID	Best for
CallSummary	`741e9ffc-87be-4bca-bb0d-f167be8b963e`	CRM-ready call recap
NextStepper	`09715241-0cdd-44c9-a386-92a1340bdf4a`	Actions and commitments (us vs them)
MeetingPrepper	`c0a76fd7-3f56-4a03-b2e7-7765da10c457`	Pre-meeting brief + questions to ask
CallQualifier	`3a7753e1-d21e-4cb7-a990-7820291274cd`	Structured qualification + gaps
DealBriefing	`1204e84f-6edd-4782-bbdf-e5e070b400cf`	Executive deal summary + risks
EmailFollowUp	`b2a9ae1b-2026-4dfa-9c67-101733a87a04`	Follow-up email draft

Example: pull next steps from a call

Find the call with search_activities, setting filters.type to call, then note its numeric call_id.
Ask Claude: "Use the NextStepper agent on call [ID] to extract every commitment. Separate our tasks from theirs, include dates."
The assistant calls ask_anything_on_call with id set to the numeric call_id and agentUuid: "09715241-0cdd-44c9-a386-92a1340bdf4a".
You get structured client-side and team-side actions with timestamps

Example: executive deal briefing

Find the deal with search_deals. To use its CRM ID in this example, translate the returned Modjo id with resolve_ids: entity: "deal", direction: "modjo_to_crm".
Ask: "Use DealBriefing on deal [CRM_ID] for an actionable briefing: status, stakeholders, signals from recent calls, risks, expected decisions, close plan." The assistant calls ask_anything_on_deal with this identifier in crmId and the DealBriefing UUID in agentUuid.
You get a document ready for forecast review or deal desk

Other relevant information (MCP V2)

Best practices

Reuse instructions for each agent. Shared instructions make analyses easier to compare, without guaranteeing identical answers.
Specify the period and combine filters. With search_activities, use filters.date_range, deal_ids, account_ids or user_ids to select conversations before analyzing them.
Read the content your question needs. Start with the full summary from get_activity_content. Request the transcript if the summary is insufficient, or to find exact wording, a speaker or a timestamp.
Ask for evidence. Ask your assistant to cite sources and relevant passages, then check the citations against the returned content.
Read the available pages. For paginated searches, pass the returned pagination.nextCursor into pagination.cursor on the next call, keeping the same filters. Stop when pagination.hasNextPage is false.
Keep your agent references. Document the name, UUID and instructions associated with each use case.
Encoding: send searches in UTF-8 and write accented characters normally.

Troubleshooting

OAuth sign-in loops or fails

Make sure you are signed in at app.modjo.ai in the same browser before restarting OAuth. If the loop persists, clear cookies for modjo.ai and sign in again.

Tools do not appear after connecting

Refresh the MCP connection in your AI tool. Check the URL https://api.mcp.modjo.ai/v1/mcp, your client’s OAuth support and the catalog enabled for your workspace.

401 / 403 errors with a bearer token

Check the API key and the Authorization: Bearer <key> header, with a space after Bearer. If the error persists, contact your Modjo admin.

A deal or account analysis times out

Check the timeout configured in your MCP client. To analyze a smaller set of conversations, select them with search_activities and read them with get_activity_content. If your question concerns one call, use ask_anything_on_call.

Data seems stale or incomplete

Check your filters, access rights and remaining pages. For a recent call, also check its availability in Modjo, then run the search again. Search metadata does not replace the full content returned by get_activity_content.

Set up and use the Modjo MCP