In Parallel

ai.in-parallelPublished by in-parallel.aiOfficial publisherv0.1.1Updated Oct 30, 2026

The context layer for your company's AI: your team's decisions, meetings and plans, with sources.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Hosted MCP server that gives an AI assistant your team's decisions, meetings and plans, with sources, scoped to your permissions.

What you can do
  • Read team context such as briefings, meetings, decisions and wiki pages
  • Catch up on priorities and find relevant decisions for a project
  • Record findings you want to share with your team
  • Check the connection to the In Parallel workspace from the assistant
When to use it
Useful when you want an assistant to answer questions grounded in your company's internal context — what needs attention this week, what was decided on a project — or to file findings back to your team instead of keeping them in a single chat.
Requirements
A remote endpoint at in-parallel.ai reached over streamable HTTP, with OAuth sign-in through your assistant app's connection flow. An In Parallel account with access to your team's workspace is required. The optional setup command for Claude Code, Codex or Cursor needs Node 20.12+ and, for Claude Code and Codex, their own CLI on your PATH.
Before you install
The assistant can read internal team context and record findings that are shared with your team, so writes are visible to colleagues. Only what the assistant sends through the In Parallel connection goes to the service. Sign-in is handled by the assistant app; the plugin's scripts do not read or store passwords or tokens. Access is scoped to each user's permissions.

Installation

In SourceWeft

  1. Open In Parallel in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.in-parallel%2Fin-parallel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "in-parallel": {
      "type": "http",
      "url": "https://www.in-parallel.ai/mcp"
    }
  }
}

README

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:

sh
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.

  1. Connect In Parallel under claude.ai → Customize → Connectors.
  2. Get the claude-projects ZIP from your administrator, or build it from a checkout of this repository with node scripts/package.js --client claude-projects. It holds the skill only, with no MCP server, hooks or scripts.
  3. 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.

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.

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

Setup and uninstall act on your user installation only. A copy installed for a single project is left in place; setup names it and the command that removes it.

doctor lists every location it checked (your user settings, the project root and the current directory, and each client's plugin registrations) as found, not found or conflicting, before it reports any error. For Claude Code it lists each In Parallel copy with its scope, the project it belongs to and its files, such as the setup copy for your user and one installed in another project. A conflicting entry says what it conflicts with and why, and a legacy entry named in-parallel comes with how to fix it. Changed installed files are named; when an installed .mcp.json gained an Authorization header, doctor says a credential header was added without printing it. It always shows the endpoint setup installed, even when a check fails. Without a setup copy, doctor lists any project copy setup did not install, says it can stay, and gives the command that removes it. It checks what is installed, not that it works: to check that, ask your agent "Check my In Parallel connection". doctor changes nothing.

Uninstall

If you used the setup command, run:

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

It removes only the files and registrations setup itself wrote, prints one line for each, and first backs the files up to ~/.in-parallel/setup/backups/. It stops without removing a file that changed since setup wrote it.

If you installed from a plugin browser, remove In Parallel there.

Need help?

Ask your assistant: “Check my In Parallel connection.”

If you can't install the plugin or access your workspace, ask your workspace administrator for help.

Publishing to the MCP registry

server.json lists the hosted In Parallel MCP server in the official MCP registry: the context layer for your company's AI, which gives Claude, ChatGPT, Copilot and other MCP clients your team's decisions, meetings and plans, with sources and scoped to each user's permissions. PulseMCP and Glama ingest new entries from the official registry; Smithery needs its own submission at smithery.ai.

Install mcp-publisher (brew install mcp-publisher) and check the file:

sh
mcp-publisher validate

The name ai.in-parallel/in-parallel needs proof that you control in-parallel.ai. Both proofs use an Ed25519 key, which needs OpenSSL 3 (brew install openssl@3; macOS LibreSSL lacks Ed25519):

sh
OPENSSL=/opt/homebrew/opt/openssl@3/bin/openssl$OPENSSL genpkey -algorithm Ed25519 -out key.pemPUBLIC_KEY="$($OPENSSL pkey -in key.pem -pubout -outform DER | tail -c 32 | base64)"PRIVATE_KEY="$($OPENSSL pkey -in key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"

Then pick one:

  • DNS. Add a TXT record on the in-parallel.ai apex (not a subdomain) with the value v=MCPv1; k=ed25519; p=${PUBLIC_KEY}, wait for dig +short TXT in-parallel.ai to show it, then run mcp-publisher login dns --domain in-parallel.ai --private-key "$PRIVATE_KEY".
  • HTTP. Serve the single line v=MCPv1; k=ed25519; p=${PUBLIC_KEY} as text/plain at https://in-parallel.ai/.well-known/mcp-registry-auth. The registry fetches the apex and does not follow redirects, so the apex-to-www redirect must skip this path. Then run mcp-publisher login http --domain in-parallel.ai --private-key "$PRIVATE_KEY".

After logging in, publish:

sh
mcp-publisher publish

Without domain access, rename the server to io.github.in-parallel-oy/in-parallel and log in with mcp-publisher login github as an Owner of the in-parallel-oy GitHub organization.

Keep key.pem out of the repo. Each published version is permanent, so bump the version and publish again when the listing should change. npm version <patch|minor|x.y.z> sets it in package.json, server.json and every plugin manifest, and commits the change.

Repository layout

Plugin directories and marketplaces install plugins/in-parallel/ only: the skill, the MCP connection, each client's manifest, LICENSE and NOTICE. The setup command, its package.json and lockfile and the build scripts stay at the repository root, outside the installed plugin. Keep plugins/in-parallel/LICENSE and plugins/in-parallel/NOTICE identical to the root copies; the tests check this.

License

Apache-2.0.

Source: README.md at commit ba84a3e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestOct 15, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts