Log inSubmit server
Agent Interop Runtime logo

Agent Interop Runtime

Coordinates local Freebuff, Codex, OpenCode, and Claude Code sessions through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Agent Interop Runtime

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "agent-interop-runtime": {
      "command": "npx",
      "args": [
        "-y",
        "agent-interop-runtime@1.1.0"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 9 tools correctly (9d ago).

Overview

Agent Interop Runtime coordinates local coding-agent sessions while preserving each provider's account, permissions, history, and project access. It discovers installed providers, lets an MCP client select or resume sessions, send work, monitor progress, request cancellation, and collect results or diffs. Shared notes, handoffs, evidence, reviews, and resource claims support coordination across sessions without merging their conversations. Use it when multiple local coding agents need to collaborate through a single MCP connection.

Use cases

  • Coordinate tasks across local coding-agent sessions
  • Route work to Freebuff, Codex, OpenCode, or Claude Code
  • Monitor provider progress and collect task results
  • Pass notes, evidence, and handoffs between sessions
  • Run approved workspace checks through an MCP client

Key features

  • Local provider discovery and capability reporting
  • Session creation, resumption, and task delivery
  • Progress monitoring, cancellation, and diff collection
  • Shared notes, handoffs, evidence, reviews, and claims
  • Selectable minimal, core, Freebuff, full, and legacy profiles
  • Read-only mode and filtered project-file access

Tools9

What Agent Interop Runtime lets your agent do. Expand a tool for its parameters.

Verified live~969 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 26d

What it can do

From the 9 tools this server returned when we ran it; 9 declare their own safety hints.

Read-only tools · 9
Network at startup3 connections
Files written at startup1
Install scriptsprepare
npm provenanceSigned build
Package age55 days
Maintainers1

Observed 2026-11-03 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 17h ago via OSV.dev · agent-interop-runtime@1.1.0 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed9Callable tools this server registers over MCP.

How Agent Interop Runtime works

What Agent Interop Runtime does

Agent Interop Runtime gives an MCP client a local coordination layer for coding-agent sessions. It can discover supported Freebuff, Codex, OpenCode, Claude Code, and Cursor sessions installed on the same computer, then expose the controls each provider supports.

The runtime keeps provider boundaries intact. Accounts, permissions, histories, project access, login flows, and consent prompts remain managed by the provider. The runtime records delivery status and provider updates, but a delivery receipt only confirms that a provider accepted work; completion requires an observed result.

When delivery becomes uncertain after a network failure, the runtime marks the request as unknown rather than replaying it. This avoids unintentionally submitting the same work twice.

How it works

An MCP client starts the runtime, preferably as a local process over standard input and output. The runtime checks which provider sessions are available, reports their supported controls, and routes work to the selected session. Provider capability depends on the provider version, local configuration, and account state.

The runtime can create or resume sessions when a provider supports those operations. It can send tasks, read progress, wait for updates, request cancellation, and retrieve provider diffs where available. Shared work records, notes, handoffs, reviews, evidence, and coordination claims allow sessions using the runtime to exchange task context.

Optional verification runs local checks inside a named workspace using programs explicitly configured by the user. These commands are not sandboxed. File access is limited to small text files in an approved project folder; common credential files are blocked, credential-shaped text is redacted, and binary files are refused.

Setup and configuration

Use Node.js 20 through 26. Install the current major release with npm or pnpm, then inspect available providers with the doctor command:

Terminal
npm install --global agent-interop-runtime@1
agent-interop-runtime doctor

A source checkout can be built with pnpm and inspected through the generated CLI. For MCP connections, start serve through a client's local-server configuration. Claude Code can register the server with a stdio command, while Codex, Cursor, and OpenCode have setup or configuration examples in the project. Other MCP clients can launch the same command through their local server settings.

Tool exposure is selectable through profiles. Pass --profile minimal, core, freebuff, full, or legacy to serve, or set INTEROP_TOOLS_PROFILE when the client cannot pass arguments. The minimal profile exposes nine focused tools; broader profiles add coordination and Freebuff-specific operations. INTEROP_READ_ONLY=1 removes tools that change provider or coordination state.

HTTP mode is intended for deliberate remote setups and requires authentication plus network protection. Session identifiers alone are not access control.

Tools and capabilities

  • Discover installed provider sessions and inspect their reported capabilities.
  • Create or resume sessions where the provider supports those actions.
  • Send work, monitor progress, wait for updates, request cancellation, and collect diffs where supported.
  • Maintain shared work notes, handoffs, evidence, reviews, and resource claims.
  • Run explicitly enabled local verification checks in a named workspace.
  • Read approved small text files with credential filtering and binary-file rejection.
  • Select a modern or legacy tool catalog based on client and migration needs.

The legacy profile preserves the original 0.3.x tool names, while modern profiles use consolidated, verb-first operations.

Limitations and notes

Finding a provider does not confirm that it is signed in or ready to accept work. Provider applications must be installed on the computer running the runtime, and the runtime cannot bypass provider login, consent, or permission requests. It also does not replace the provider's own application or merge separate accounts and histories.

Resource claims coordinate agents that use this runtime but cannot prevent unrelated programs from editing the same files. Verification commands run with the access available to the user's account, so they should only be used with trusted work and commands. Automated checks and offline benchmarks use simulated providers rather than live sessions and do not measure speed or provider cost.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Agent Interop Runtime

Agent Interop Runtime is an MCP server that connects local MCP clients to Freebuff, Codex, OpenCode, Claude Code, and Cursor sessions. Its main tools discover providers, select or resume sessions, send work, monitor progress, request cancellation, collect results or diffs, and coordinate handoffs without merging provider accounts or histories.

Install it with npm or pnpm using the package's current major release, then run `agent-interop-runtime doctor` to inspect local providers. The runtime requires Node.js 20 through 26. You can also clone the source repository, install dependencies with pnpm, build it, and run the generated CLI.

Choose a profile with `serve --profile <profile>` or set `INTEROP_TOOLS_PROFILE`. `minimal` is the nine-tool starting set; `core`, `freebuff`, and `full` expose broader capabilities, while `legacy` preserves the original 0.3.x names for migration.

Yes, Cursor is a supported provider and has a setup command that writes a user-level MCP entry, with an option to limit the connection to the current project. The runtime uses Cursor's supported Agent Client Protocol commands, and available controls depend on the local provider setup.

No, verification commands are not sandboxed. They run with the access available to the user's account and only after verification is explicitly enabled, so use them with trusted work and commands. File reads are more restricted: credential files are blocked, credential-shaped text is redacted, and binary files are refused.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAgent Interop Runtime AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/agent-interop-runtime?style=directory)](https://allmcps.com/mcp/agent-interop-runtime)
HTML Embed
<a href="https://allmcps.com/mcp/agent-interop-runtime"><img src="https://allmcps.com/api/badge/agent-interop-runtime?style=directory" alt="Agent Interop Runtime on AllMCPs" /></a>