Roadmap. Shipped, now, next.

What we have released, what we are working on, and the order of what comes after. Plans carry no dates — only order, and only what we intend to build.

  • Shipped
  • Now
  • Next
  • Not planned

Shipped

Released and available today, newest first.

  1. Plugin servicev1.3.2

    latest means the newest version

    latest now picks the highest version compared as numbers (v1.36.11 over v1.36.9). The MCP endpoint reports the running release and returns lowerCamelCase fields throughout.

  2. protoc-gen-mcpv1.0.0

    protoc-gen-mcp 1.0

    Go on the official MCP Go SDK; Python, TypeScript, Java and Kotlin at parity with it. Tools, resources and prompts in every language, OAuth for HTTP servers, MCP Apps UI metadata.

  3. Plugin service

    Public plugin registry: plugins.easyp.tech

    80 plugins and 1,700+ versions — Go, gRPC, Connect, TypeScript, Python, Java, Rust, Swift and more — ready to use from easyp.yaml without installing anything.

  4. Plugin servicev1.3.0

    Reproducible plugin packs

    The same plugin always packs to the same bytes, and plugins are built for the platform the service runs on.

  5. Plugin servicev1.2.0

    Helm StatefulSet and one-pass publishing

    Each replica gets its own plugin cache volume; plugins publish builds, verifies, uploads and registers in a single pass.

  6. easyp CLIv1 preview

    easyp v1 nightly builds

    New config (protobuf.mod / protobuf.lock, nested Git modules, replace), migrate from v0, get, mod tidy, descriptor-based breaking checks, EASYP_PROXY.

  7. Plugin servicev1.1.0

    Interpreted plugins run anywhere

    22 plugins built on Python, Node or the JVM became relocatable bundles, verified when they are built.

  8. protoc-gen-mcp

    protoc-gen-mcp in awesome-go

    Listed in the awesome-go catalogue.

  9. Plugin servicev1.0.0

    Plugin service 1.0

    First stable release: remote code generation over gRPC with a frozen API contract, a Go SDK, and community and enterprise tiers.

Now and next

Per product: what is in progress, then what follows, in order.

easyp CLI

A drop-in buf replacement

Now

  1. easyp 1.0 stable

    The v1 configuration and commands from the nightlies, as a stable release.

  2. breaking — the same findings as buf

    Including positions.

  3. easyp build

    Compile to descriptor sets without a generate config.

  4. easyp format

    -w, --diff, --exit-code, --stdin-filepath.

  5. easyp migrate --from-buf

    buf.yaml, buf.gen.yaml and buf.lock to easyp configs in one command.

  6. Compatibility checked every night

    Against the latest buf and protoc; editions 2023 and 2024; Windows in CI.

Next

  1. Language server

    Diagnostics, go to definition, hover, formatting; then completion, references, rename.

  2. VS Code extension, then JetBrains plugin

  3. Only what changed

    --changed-since for lint, generate, breaking, build and format.

  4. easyp changelog

    API changes between two refs as Markdown, and as a PR comment.

  5. easyp mod outdated and easyp docs

  6. easyp init --from-protoc

    Turn a protoc command line into an easyp config.

  7. More commands

    config ls-lint-rules, PROTOVALIDATE rule, mod graph, export, stats, convert, source edit deprecate, custom rules as wasm plugins.

Plugin service

Your plugins, run for you

Now

  1. Generation result cache

    The same request with the same plugin is answered without running it.

  2. Smaller, faster requests

    Compressed requests and a faster plugin cold start.

  3. protoc-gen-mcp in the registry

  4. easyp-svc migrate down

    Run the migration rollbacks that already exist.

  5. A slimmer Go SDK

    Without the MCP dependencies for clients that do not need them.

Next

  1. Plugin sandbox

    WebAssembly where a plugin builds to it, OS-level isolation for the rest.

  2. Users and permissions

    Organisations, roles, plugin owners, SSO and OIDC; mTLS identities.

  3. Generated SDKs

    go get, npm, pip and Maven packages with generated code.

  4. Catalogue

    More plugins, automatic version updates, signed plugin archives and provenance.

  5. Code generation over MCP

    So an agent can call the service itself.

protoc-gen-mcp

Any proto service → an MCP server

Now

  1. Swift target

    Merged; ships in the next release.

  2. Long tool names

    Shortened to 64 characters with a hash instead of failing generation.

  3. Every language checked in CI with MCP Inspector

Next

  1. gRPC pass-through

    The generated server calls your existing gRPC service — no handlers to write.

  2. Strict schemas

    For OpenAI, Gemini and Anthropic strict mode.

  3. Server-streaming RPCs and progress notifications

  4. Elicitation, sampling and completions

  5. Typed MCP clients

  6. OpenTelemetry tracing and metrics

AI agents

Schemas your agent checks itself

Now

Starts together with the language server: both need the same diagnostics, symbol search and formatting.

Next

  1. easyp mcp

    An MCP server in the CLI: lint, breaking, build, format, generate, symbol search — answers in JSON.

  2. Skills, hooks and ready-made commands

    An agent that edits a .proto file formats and lints it, and fixes its own mistakes.

  3. Claude Code plugin

  4. OpenAI Codex

  5. Gemini CLI and Antigravity

  6. Cursor, then GitHub Copilot, then Grok

  7. Windsurf, Zed, JetBrains AI, Cline

Not planned

buf’s cloud commands. EasyP works differently: dependencies come from Git, plugins from a service you can run yourself.

  • push
  • registry *
  • beta registry *
  • policy
  • price
  • studio-agent
  • webhook

If one of these is what keeps you on buf, tell us — that is exactly the feedback this list is for.

Missing something?

Open an issue or write to us in Telegram. What people ask for moves things up this page.