OXP — Build once. Run across every IDE.

Runtime v0.1 shipped · VS Code · JetBrains · Neovim<br>Build one extension. Run across every IDE.<br>VS Code · JetBrains · Neovim · Cursor · Windsurf — write it once, ship it everywhere on the open OXP runtime.

Search

Popular:reactpythonthemesgitaijupyter

2,514<br>MCP Servers

Compatible IDEs

Open<br>Protocol

Built in<br>Europe

VS CodeVS Code<br>CursorCursor<br>WindsurfWindsurf<br>JetBrainsJetBrains<br>NeovimNeovim<br>VS CodeVS Code<br>CursorCursor<br>WindsurfWindsurf<br>JetBrainsJetBrains<br>NeovimNeovim

Shipping next

v0.1 is live. v0.2 is already in flight.<br>Specified in WIT. Implemented on all three hosts. Rolling out as soon as conformance tests go green — no waiting on a 2027 milestone.

Native UI surfaces<br>ui/render painted into real tool windows on JetBrains and floating windows on Neovim. Same component vocabulary, native pixels.

Streams<br>Long-running stream/* RPCs for log tailing, build output, and incremental search — backpressure-aware on every host.

editor/* APIs<br>Read selections, apply edits, decorate ranges, and register code lenses through one editor contract that lowers to each host's native API.

surface/register<br>Declarative panel + view registration. One manifest entry, native chrome on every editor.

// Why OXP

The problem is 30 years old. We just solved it.

Portability

One bundle. Every editor. No compromises.<br>You wrote it once. It runs everywhere. Not mostly everywhere or with a few tweaks — everywhere. The .oxp runtime is a contract, not a suggestion.<br>Zero background processes<br>Universal API surface<br>Portable across every conformant runtime<br>Read the docs

Modern Stack

Your stack. Not ours.<br>React, Vite, Tailwind. The tools you already know. No proprietary APIs to memorize, no XML to hand-roll, no webview hacks to maintain. Just code.<br>Sandboxed micro-frontends<br>Declarative permissions (oxp.config.ts)<br>60fps native rendering<br>Explore the engine

Install the CLI<br>$ npm i -g @oxprotocol/cli

Copy2<br>Scaffold locally<br>$ npx @oxprotocol/cli create my-extension

Copy3<br>Reserve a slug<br>Claim @you/your-extension on the registry

Full getting-started guide →

// Trending Extensions

What the community is building

View all<br>No extensions found matching ""<br>Try a different search term or browse all extensions

AI Ready

MCP Servers

Every AI tool installed into every editor. One command.<br>MCP$ oxp install @modelcontextprotocol/server-githubCopy

// MCP Library

2,514 AI tools. One command.<br>Every MCP server ever published, indexed daily. While everyone else edits JSON config files, your users type one command.<br>$ oxp mcp add githubInstant

Browse MCP Library

Fetch<br>@modelcontextprotocol

Featured

Fetch URLs and convert HTML to markdown so agents can read the live web.<br>stdio

Filesystem<br>@modelcontextprotocol

Featured

Secure local filesystem access for MCP clients. Read, write, search, and watch files within sandboxed directories.<br>stdio

Git<br>@modelcontextprotocol

Featured

Inspect git history, diffs, branches, and blame from any MCP-aware agent without shelling out.<br>stdio

GitHub<br>@modelcontextprotocol

Featured

Issues, pull requests, code search, and repo metadata over the GitHub API as MCP tools.<br>stdiohttp

Memory<br>@modelcontextprotocol

Featured

Persistent knowledge-graph memory store for long-running agent sessions.<br>stdio

Postgres<br>@modelcontextprotocol

Featured

Read-only SQL execution and schema introspection over a Postgres connection.<br>stdio

The extension ecosystem just changed.<br>Be the first to build on it.<br>Get StartedRead the Docs

Online