Connect your AI tool to In Parallel - In Parallel help

Connect your AI tool to In Parallel

Connect Claude, ChatGPT, Cursor, or Microsoft 365 Copilot to In Parallel so your AI assistant can read your meetings, goals, and Workspaces — and act on them — directly from a…

Connect Claude, ChatGPT, Cursor, or Microsoft 365 Copilot to In Parallel so your AI assistant can read your meetings, goals, and Workspaces — and act on them — directly from a chat.

In Parallel exposes its data and actions through the Model Context Protocol (MCP), the open standard AI clients use to talk to external tools. Once connected, your AI tool can look up your meeting records, list decisions and action items, run an execution-health check, and more — all within the access you grant.

Before you start

  • You need an In Parallel account.
  • For a direct MCP connection, you need Claude, ChatGPT, or Cursor installed or open. Point that client at https://www.in-parallel.ai/mcp.
  • For Microsoft 365 Copilot, add the In Parallel agent from the Microsoft Marketplace (Teams / Microsoft 365 app store). Depending on your organization’s policies, an administrator may need to approve or install it first.

See Using In Parallel with Microsoft 365 Copilot for the Marketplace-agent setup. Do not enter the raw MCP URL in Copilot. GitHub Copilot is a separate product and is not covered by that walkthrough.

The direct-connection walkthroughs below finish at an In Parallel OAuth consent screen where you choose which Workspaces to share and click Allow access. Copilot reaches the same consent screen after you invoke the Marketplace agent. If you’ve connected an AI tool before, that step will look familiar.

Connect Claude

Follow Connect Claude to In Parallel for the current connector navigation and account requirements. Use https://www.in-parallel.ai/mcp as the server URL, connect your account, and review which Workspaces to share on the In Parallel consent screen.

Review the connector’s tool permissions before allowing write or delete actions.

Connect ChatGPT

Follow Connect ChatGPT to In Parallel for the current plugin or app setup available to your account. Use https://www.in-parallel.ai/mcp and OAuth authentication, then review the Workspaces requested on the In Parallel consent screen.

Client menus and availability change independently of In Parallel. The client-specific guides distinguish the current setup from older desktop and app layouts.

Connect Cursor

Cursor is supported. Add In Parallel as an MCP server in Cursor’s settings, using the same MCP URL — https://www.in-parallel.ai/mcp — and complete the OAuth consent step described above (choose your Workspaces, then Allow access). Cursor’s MCP configuration changes occasionally as the client evolves, so follow Cursor’s own MCP setup docs for the exact location of the server config.

Microsoft 365 Copilot is supported through the In Parallel Marketplace agent — see Using In Parallel with Microsoft 365 Copilot. This is Microsoft’s workplace Copilot, not GitHub Copilot.

What can it do once connected?

Once connected, your AI tool can read from In Parallel — your meetings, goals, decisions, action items, and Workspaces — and run available actions such as creating an action item. Trust the live tool list: older accounts may also expose the get_drift_report execution-health diagnostic. When it is absent, list_action_items can filter overdue work, while list_decisions, list_risks, and list_open_questions let you inspect those current records; the combined stale-and-unresolved diagnostic itself is unavailable. Each In Parallel tool has a clear, human-readable title so your AI client picks the right one. For the full set, see the In Parallel MCP tools reference.

You stay in control of what it can do: per-tool permissions let you require approval before any write or delete tool runs, or block specific tools entirely (see the Claude connection guide). Write and delete tools require approval by default.

What’s next

  • In Parallel MCP tools reference — the full set of tools a connected assistant can use, and which ones read versus write.
  • Use the In Parallel MCP with Jira in Claude — keep a Jira board in sync with your execution layer from a single AI chat.
  • MCP privacy: mask people in AI responses — hide real names and emails from your connected assistant while it works.
  • Integrations — overview of everything In Parallel connects to, and what each connection does.
  • Prefer an API-key connection? If OAuth can’t complete — for example headless agents, CI runners, or restricted environments — contact your In Parallel customer success manager to request an API key for your AI client.
  • Run work with AI — hand a meeting observation to your connected AI tool with a pre-rendered prompt.