Spec Driven Development
제작자: formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치
Agent Interop Runtime
개요
제작자가 쓴 설명(영어 원문)
Coordinate coding agents through a local MCP server while keeping accounts and workspaces separate.
PopNx MCP의 세 기둥
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
- 사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
- 우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
- 사용 정도i아직 측정 안 함★ –
할 수 있는 일
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
- 연결 방식: 내 컴퓨터에서 실행
- 전송 방식: stdio
- 카테고리: 기타
설치
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
설치하기 전에
- 기본 점검: 1개 중 1개 통과
- 내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
- 레지스트리에 입력해야 할 키가 나와 있지 않아요.
필요한 것
- npmNode.js 설치(npx 명령어용)
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"agent-interop-runtime": {
"command": "npx",
"args": [
"-y",
"agent-interop-runtime"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add agent-interop-runtime -- npx -y agent-interop-runtime또는 설정을 직접 복사하기
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"agent-interop-runtime": {
"command": "npx",
"args": [
"-y",
"agent-interop-runtime"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
또는 설정을 직접 복사하기
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"agent-interop-runtime": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agent-interop-runtime"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
할 수 있는 일
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
기본 점검i
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
- ✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 Praket7 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
- … 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- … 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- – 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
- – 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
- … 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
기타 카테고리의 다른 서버와 비교i
- 이 카테고리의 다른 서버 32435개 중 0%보다 스타가 많아요
- 이 카테고리의 다른 서버 32435개 중 94%보다 최근에 레지스트리에 공개됐어요
- 기본 점검 결과가 이 카테고리의 다른 서버 32435개 중 100%와 같거나 더 좋아요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
자주 묻는 질문
Agent Interop Runtime, 안전한가요?
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
어떤 키나 코드가 필요한가요?
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
아직 관리되고 있나요?
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.1.0)은 그저께 레지스트리에 올라왔어요.
어떤 앱에서 쓸 수 있나요?
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
대신 쓸 수 있는 건 뭐가 있나요?
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
대안
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Remote Desktop Commander
제작자: desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
클라우드에서 실행★ 211어제 업데이트
설치
Apify MCP Server
제작자: apify
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
클라우드에서 실행오늘 업데이트
설치
제작자의 README
README 열기
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Agent Interop Runtime
Your coding agents already know how to work, and Agent Interop Runtime helps them share a task while each one keeps its own identity, account, and working environment.
Connect a local MCP client to the runtime, and it will find the coding agents installed on your computer so you can choose a session, send it work, follow its progress, and pass a result to another session. Each provider still uses its own account, permissions, history, and project access, so the runtime coordinates the work without merging separate environments.
Think of it as a traffic desk for coding agents, because it shows which session received a task, records the updates that provider sends back, and keeps the result of each check in one place without turning separate conversations into a shared chat.
Watch the short illustrated tour
These pictures are illustrations, so they explain the workflow and available measurements but do not show a live provider session.
What happens when you send work
The runtime sends your message to the provider session you selected, and the receipt may confirm that the provider accepted it; however, acceptance only confirms delivery to the provider and does not mean the agent finished the task. The runtime reports completion only after it observes a result from that session.
The same rule applies when delivery is uncertain, because a network failure may happen after the provider accepted your message but before the runtime received confirmation. In that case the runtime marks delivery as unknown and does not silently send the prompt again, which avoids repeating work that may already be underway.
What it can do
Find supported provider sessions on your computer, so you can see which local tools are available before choosing where to send work.
Create or resume sessions when the selected provider supports those actions, and use the provider report to check which controls are available in your setup.
Send work, request cancellation, read progress, and collect a provider diff when the selected provider supports those features.
Keep shared work notes, handoffs, evidence, reviews, and cooperative resource claims so participating sessions can coordinate around the same task.
Run local checks inside a named workspace when you explicitly enable verification, and review the configured programs before trusting them with a project.
Read small text files inside an approved project folder, while common credential files are blocked, credential shaped text is redacted, and binary files are refused.
Provider features differ, so the doctor report shows what each installed provider can do; finding a provider alone does not confirm its sign in status or whether it is ready to accept work.
What it does not do
It does not merge provider accounts or histories, and each session remains subject to its provider's own settings.
It does not bypass a login, consent prompt, or permission request, so you must complete those steps through the provider itself.
It does not give an agent access to a provider that is not installed on the computer running the runtime, nor does it replace that provider's own application.
It does not sandbox commands, because verification runs the programs you configure with the access available to your account, so use it only with work and commands you trust.
Resource claims coordinate agents that use this runtime, but they cannot stop another program from editing the same files outside the runtime.
Providers
Freebuff Desktop uses its local app connection, and writes require a current launch check before work is sent; Freebuff CLI instead uses a managed terminal session.
OpenCode uses its local server, which the runtime may start on loopback when needed, and requests that may change work are never replayed after an uncertain network result. Each session remains tied to the server that exposed it, so switching servers does not silently redirect existing work.
Codex uses the Codex app server, while Claude Code and Cursor use their supported Agent Client Protocol commands.
The available features depend on the provider version, local setup, and account state, and most protocol checks use simulated providers rather than live sessions. Check the provider on the computer that will run the MCP server before relying on it for live work.
MCP protocol support
The server supports the 2026-07-28 MCP protocol and the earlier 2025-11-25 protocol, so newer clients can negotiate the per-request protocol while existing clients keep their session-based connection. This works over stdio and Streamable HTTP, and both versions receive the same selected tools and provider behavior.
Choose the tools your client sees
The runtime starts with a focused set of nine tools, so a new MCP connection can find providers, inspect and control sessions, read events, and cancel or resume work without loading the larger coordination catalog. You can choose a larger set when your work needs shared conversations, evidence, handoffs, or Freebuff specific controls, and you can keep the original 0.3.x names while migrating an existing client.
| Profile | Tools | Use it when |
|---|---|---|
minimal | 9 | You want the recommended starting set for provider sessions. |
core | 30 | You also need shared conversations, work records, handoffs, reviews, evidence, and claims. |
freebuff | 16 | You mainly work with Freebuff projects and threads. |
full | 49 | You need the modern names for every supported feature. |
legacy | 52 | An existing MCP client still calls the original 0.3.x tool names. |
The modern profiles use predictable verb first names, and related progress operations have been combined so one tool can read a snapshot or wait for updates. The legacy profile preserves the previous names during migration, while the migration guide maps each older tool to its new name or replacement.
Choose a profile on the server command, or set INTEROP_TOOLS_PROFILE when your client configuration cannot pass an argument.
npx -y agent-interop-runtime@1.1.0 serve --profile minimalnpx -y agent-interop-runtime@1.1.0 serve --profile core npx -y agent-interop-runtime@1.1.0 serve --profile freebuff npx -y agent-interop-runtime@1.1.0 serve --profile full npx -y agent-interop-runtime@1.1.0 serve --profile legacy
Read only mode removes tools that change provider or coordination state, and it can be enabled by setting INTEROP_READ_ONLY=1 in the server environment.
Install
Use Node 20 through Node 26, and install the current major release with npm or pnpm before checking which providers are available.
npm install --global agent-interop-runtime@1agent-interop-runtime doctor
You can also use the source checkout when you are changing the project, and its build runs the same TypeScript compiler used by the release workflow.
git clone https://github.com/Praket7/agent-interop-runtime.gitcd agent-interop-runtime pnpm install pnpm build node dist/src/cli.js doctor
Connect a local MCP client
The runtime talks to provider apps and tools installed on the same computer, so the recommended connection is a local MCP server over standard input and output. Start with the setup command for your client, and restart or reload that client after changing its configuration.
Codex
The installer adds or repairs the local Codex entry, backs up the existing configuration before changing it, and preserves unrelated settings.
npx -y agent-interop-runtime@1.1.0 install --writeCursor
The Cursor installer writes a project independent entry in your user configuration, and --project can be added when you want the connection only in the current project.
npx -y agent-interop-runtime@1.1.0 cursor-setup --writeClaude Code
Claude Code can launch the local server directly, and the command below starts with the recommended nine tools.
claude mcp add --transport stdio agent-interop-runtime -- npx -y agent-interop-runtime@1 serve --profile minimalOpenCode
Add the following entry to your OpenCode configuration, and the local process will expose the same focused tool set.
{"$schema": "https://opencode.ai/config.json", "mcp": { "agent-interop-runtime": { "type": "local", "command": ["npx", "-y", "agent-interop-runtime@1", "serve", "--profile", "minimal"], "enabled": true } } }
Other MCP clients can launch the same serve command through their local server configuration, and the provider applications must be available on the computer running the runtime. HTTP mode can support a deliberate remote setup, but it needs authentication and network protection because session identifiers do not replace access control.
Current evidence
Automated tests and offline benchmarks check the tool behavior with simulated providers, and those results do not contact live agents, measure speed, or estimate provider cost. GitHub CI checks three operating systems against four supported Node versions, for twelve combinations.
Earlier local checks observed a response from Freebuff GLM 5.3 Flash, and OpenCode Big Pickle accepted a prompt, although completion was not observed in that session. Those observations apply only to the specific sessions tested, so they do not establish general provider support.
Run checks
pnpm typecheckpnpm test pnpm lint pnpm mcp:validate pnpm schema:check pnpm bench:check pnpm audit --prod --audit-level=high npm audit --prefix media/remotion --audit-level=high pnpm pack:check
Read the provider guide, the plain language architecture guide, the compatibility notes, the 1.0 migration guide, and troubleshooting for setup and behavior details.
Safety and privacy
The local standard input and output server is the simplest setup, while HTTP mode binds to loopback by default and requires a bearer token. Remote access requires an explicit setting and network protection, because session identifiers do not replace authentication.
Project file reads stay inside the selected project folder, and common credential files are denied while text is checked against common credential patterns. These checks cannot detect every secret, so keep sensitive values out of files an agent can read.
Verification is off by default, but when enabled it runs configured programs without a shell and checks that the working folder stays inside the named workspace. Child programs are not sandboxed, so they retain the access granted by your account.
Help improve it
Use doctor before sending work, and when reporting a problem include the provider name, version, operating system, the action you tried, and whether the provider accepted the task or returned a completed result. Leave private prompts and credentials out of reports.
The project welcomes reproducible compatibility reports and code contributions, especially when they explain what happened on a specific provider version and computer.