In Parallel MCP server

In Parallel

Bring your team's context into conversations with your AI assistant. Catch up on priorities, find relevant decisions, and share useful findings with your team.

Get started

You'll need an In Parallel account with access to your team's workspace.

Claude Code, Codex, or Cursor

Run the setup command. It asks which assistants to set up, then installs for your user:

npx -y github:in-parallel-oy/agent-plugin

Needs Node 20.12+. Claude Code and Codex also need their own CLI on your PATH. Cursor users should reload Cursor afterwards.

Later on, the same command takes doctor to check the installation and uninstall to remove it. Add --help for everything else.

Claude Desktop or ChatGPT

Open the app's plugin browser and install In Parallel from your team's plugin library. If it isn't listed, add https://github.com/in-parallel-oy/agent-plugin as a plugin source, or ask your administrator to make it available.

Claude Projects

Threads in a Claude project reach In Parallel through your claude.ai connector; the project conversation itself can't use In Parallel, only its threads can.

checkout of this repository with node scripts/package.js --client claude-projects. It holds the skill only, with no MCP server, hooks or scripts.

1. Connect In Parallel under claude.ai → Customize → Connectors.
2. Get the claude-projects ZIP from your administrator, or build it from a

1. Add it in Project settings → Plugins.

If your workspace offers it, Copy instructions for a Claude project on the workspace's What's set up page gives you project instructions to paste in.

Then

Sign in to In Parallel, choose the workspaces you want to connect, and start a new conversation with your assistant.

Try it

• “What needs my attention this week?”
• “Catch me up on [project].”
• “Record this finding for my team: …”

What the plugin does on your machine

The plugin has two parts: the in-parallel skill and a connection to the In Parallel server. It runs no hooks or scripts on your machine and keeps no local files. The files under experimental/ and the hook scripts in scripts/ are not part of it; see Experimental features.

What is sent to In Parallel

Only what your assistant sends through the In Parallel connection (https://www.in-parallel.ai/mcp unless you chose another environment during setup). The skill asks your assistant to:

• read team context, such as briefings, meetings, decisions and wiki pages
• record findings you want to share with your team

Sign-in

You sign in through your assistant app's connection sign-in, which opens In Parallel in your browser. The app keeps the sign-in. The plugin's scripts never see, read or store a password or token.

The setup command

npx -y github:in-parallel-oy/agent-plugin downloads this repository and its two setup dependencies. It copies the plugin to ~/.in-parallel/setup/ for Claude Code and Codex, or ~/.cursor/plugins/local/in-parallel for Cursor, and registers it with the claude or codex command. It writes your chosen server URL into that copy. For the Development environment or a custom server, it also adds the experimental features.

Before it installs, it reads your existing MCP settings to find a conflicting In Parallel entry: ~/.claude.json (or the one in CLAUDECONFIGDIR), .mcp.json in the current project, and ~/.cursor/mcp.json and .cursor/mcp.json. It never changes those files.

Uninstall

If you used the setup command, run:

npx -y github:in-parallel-oy/agent-plugin uninstall

If you installed from a plugin browser, remove In Parallel there. If you used the experimental work journal, also delete ~/.in-parallel to remove its local cache.

Experimental features

Shortened. The full README is on GitHub.