Skip to content

Connect an AI Client with MCP

Junto runs an MCP server, so you can connect Claude, ChatGPT, Copilot, or any other MCP-compatible AI client and work your tickets, companies, and documentation from there without switching tabs.

The MCP page in the Junto sidebar is available to every member of your organization, on every plan. You do not need admin access to connect a client.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets an AI client call tools in another product. When you connect your client to Junto, it can search tickets, look up companies and contacts, check devices, read documentation, and, with your approval, make changes in your connected integrations, all through the same conversation you already use.

Every action runs as you: your client only sees the integrations and companies you can see in Junto, and everything it does is recorded in the audit log.

Connect Your Client

  1. In Junto, open MCP from the sidebar.
  2. Under Server URL, click Copy.
  3. Follow the steps for your client below.

Paid Claude plan required

The Claude connector steps require a paid Claude plan. The same server URL works with any client that supports custom MCP connectors.

Claude Desktop

  1. In Claude Desktop, go to Settings > Connectors and choose Add custom connector.
  2. Name it Junto and paste the server URL.
  3. A browser window opens. Sign in with the same account you use for Junto.
  4. Turn on the Junto connector in a chat and try: "What tickets came in overnight?"

claude.ai

  1. In claude.ai, go to Settings > Connectors and choose Add custom connector.
  2. Name it Junto and paste the server URL.
  3. When prompted, sign in with the same account you use for Junto.
  4. Enable the connector in a chat and try: "What's breaching SLA today?"

Claude Code

Copy the one-line command shown on the Claude Code tab of the MCP page and run it in your terminal. The connector opens a browser window to sign in the first time you run a Junto tool.

Other Clients

Junto uses standard MCP over HTTP with browser-based sign-in, so any MCP-compatible client can connect. The Other clients tab on the MCP page lists the settings your client will ask for:

SettingValue
TransportStreamable HTTP
AuthenticationOAuth 2.1 (browser sign-in)
EndpointThe server URL from the MCP page

There are no API keys to create or store. You connect by signing in, and you can disconnect at any time by removing the connector from your client.

What You Can Ask

Once connected, your client can use every integration that is connected to your Junto organization. A few examples:

  • "Show me the open tickets for Acme Corp and summarize the oldest three."
  • "Which devices at Contoso haven't checked in this week?"
  • "Find the documentation for Acme's firewall and give me the management URL."
  • "Add a note to ticket 1610 saying I've called the user back."
  • "Log 30 minutes on ticket 1610 for troubleshooting the Outlook profile."

The Integrations section of the MCP page shows which integrations are connected. If none are, ask an administrator to connect one under Settings > Integrations.

Tools and Approvals

The Tools section of the MCP page lists every tool your client can call, grouped by integration. Each tool has a badge:

BadgeMeaning
ReadLooks up information. Runs immediately.
Requires approvalChanges data. Waits for a human to approve it unless auto-approval applies (see below).
Upgrade requiredAvailable on paid plans only. The rest of the tool catalog is available on every plan.

How approvals work

When your client tries to run a tool that changes data, Junto does not run it right away. Instead, the client receives an approval link and shows it to you. Open the link, review the action, and approve or deny it. Once approved, the client completes the action.

High-risk actions such as deletions, purchases, and anything that cannot be undone always require approval. So does any tool your organization has set to Requires Approval under Settings > AI Settings > Toolsets (see tool approval policies).

Skip the prompt for lower-risk actions

If your administrator allows it, you can let your client run lower-risk actions without asking you each time. Under Approvals on the MCP page, turn on either or both:

  • Low-risk actions -- Notes, time entries, and other easily reversed changes run without asking.
  • Medium-risk actions -- Ticket and record updates run without asking. These are reversible, but visible to customers.

A toggle only appears if your organization has opened that risk level to your role. If you see "Every action from your connected clients asks for approval", your role is not currently allowed to skip the prompt.

If an administrator later restricts your role, any toggle you had on stays visible so you can turn it off, but it no longer takes effect.

Administrator Settings

Administrators see an extra card under Approvals that controls which roles may turn off the approval prompt for themselves. There is one slider for Low-risk actions and one for Medium-risk actions.

Each slider runs from Nobody through Owners, Admins, Managers, and Operators to Technicians. Dragging right extends the privilege further down the role hierarchy, so setting a slider to Managers allows owners, admins, and managers to skip the prompt for that risk level.

Two rules apply regardless of the slider position:

  • High-risk actions always require approval.
  • A tool set to Requires Approval in Settings > AI Settings > Toolsets keeps prompting.

Members still choose whether to use the privilege. Opening a risk level to a role does not turn auto-approval on for anyone; each person opts in on their own MCP page.

Everything Is Logged

Every call made through a connected AI client is recorded under Settings > Audit Log on the MCP Calls tab, alongside the tool uses and action requests from the in-app agent. Administrators can filter and export the log for compliance reviews.

Troubleshooting

ProblemWhat to check
Sign-in window doesn't openAllow popups for your AI client, or open the sign-in link it shows you in a browser.
"No integrations connected yet"Ask an administrator to connect an integration under Settings > Integrations. Tools appear once an integration is connected.
A tool is missing from the listCheck whether it is disabled under Settings > AI Settings > Toolsets. Tools marked Upgrade required need a paid plan.
The client asks for approval every timeYour role may not be allowed to skip the prompt, or the action is high risk. Ask an administrator to check the sliders under Approvals on the MCP page.
The client returns results for the wrong companyThe client only sees companies you can see in Junto. Name the company explicitly in your request, since company names match exactly.