"Sailfish OS" matching MCP servers:

MCP bridge server for patchwork-os. Boots a stdio-HTTP bridge with MCP introspection over /mcp, supporting tools/list and the full MCP protocol over HTTP.

Provides TypeScript and JavaScript code refactoring operations using ts-morph, allowing AST-based symbol renaming, file/folder renaming, reference searching, and path alias removal when integrated with editor extensions like Cursor.

Run DeepSeek as a real sub-agent inside Claude Code / Codex CLI — not just a single LLM call. DeepSeek gets its own 7-tool agent loop (Read/Write/Edit/Bash/Glob/Grep/NotebookEdit) inside a sandboxed workspace.

Enables Codex to delegate review and implementation tasks to the local Qoder CN CLI as background jobs, with two permission tiers and polling-based status updates.

A local stdio MCP service that unifies coding agents like Codex and Claude into cs_agent_* tools, enabling the root agent to create, invoke, and manage child agents with recursive delegation.

Exposes the local Claude Code CLI as a subagent for Codex, enabling background review and implementation jobs with two fixed permission tiers.

Delegates work from MCP clients (like Claude Code) to the Codex CLI, allowing spawning of autonomous Codex subagents for tasks.

A comprehensive MCP server providing tools for AI agents to interact with code, including reading symbols, importing modules, replacing text, and sending OS notifications.

Enables AI coding agents to review Swift code, scaffold new iOS apps, and build, test, and preview them in the Xcode Simulator using local Apple guides and source references.

Bridges a main agent (e.g., Codex) to a separate execution model in Claude Code Haha Desktop, enabling delegated coding tasks with file modifications, test runs, and change auditing.

Enables Claude Code to access and operate an IBM z/OS mainframe via TN3270, including reading screens, browsing datasets, editing code, submitting jobs, and running regression tests through natural language.

A tiny Hermes-friendly bridge that exposes oh-my-pi's CLI as MCP tools (prompt and doctor) for code generation and environment verification.

Bridges the ChatGPT web UI to a local development environment over MCP, letting the model read and patch files, run real shell commands and terminals, execute tests, and control the desktop (screen, mouse, keyboard, clipboard) within user-approved folders. It adds parallel workers, goal/loop long-task control, plugin tools, and a security-hardening layer with risk-tiered shell policy, audit logging, and credential sanitization.

An MCP server that provides TypeScript 7 native language server capabilities (go to definition, find references, hover types, diagnostics) to coding agents, using the Go-based tsc compiler for fast and accurate semantic analysis.

Send requests to OpenAI, MistralAI, Anthropic, xAI, or Google AI using MCP protocol via tool or predefined prompts. Vendor API key required. Both STDIO and SSE transport mechanisms are supported via arguments.

Exposes a running DeepSeek Harness as an MCP endpoint so any other agent or script can create workspaces and sessions, hand coding tasks to the DSH agent, read and write files, run shell commands, and invoke permitted harness tools under the same sandbox, transcript, and permission policy as the DSH UI.

Enables dispatching entire autonomous multi-agent engineering swarms directly from IDEs like Cursor and Windsurf via a single MCP endpoint, with streaming progress updates and verified git diffs returned to the editor.

A Model Context Protocol (MCP) gateway for running Claude Code, Codex, Gemini, Grok, and Mistral (Vibe) CLIs from one MCP endpoint, with durable async jobs, session continuity, cache-aware prompting, observability, and personal-appliance setup tooling. Why developers try it: one local MCP endpoint for cross-LLM validation, multi-agent coding workflows.

Enables Claude Code, Cursor, and other AI tools to call OpenAI Codex for task execution, with safe and writable modes.

Enforces a git-tracked, code-checked finite state machine that hands control between a planning director and a local Ollama implementor, exposing tools to check phase status, transition states, and run the implementor to execute plan step files one at a time. It enables a project to be planned, implemented step by step with per-step test gating, and validated before completion.