Connect Protocol for Ktor servers
Add Connect beside REST.
Migrate in small cuts.
Connect-Ktor brings the Connect Protocol to existing Ktor apps without asking them to abandon REST. Same process, typed RPCs, gradual adoption.
Unofficial library. Connect-Ktor is a community project, not published by the ConnectRPC organization. It extends Connect-Kotlin for Ktor and tracks the Connect conformance suite independently. For Connect itself, Connect-Kotlin clients, or the protocol, see the official connectrpc.com docs.
Why teams use it
Production Ktor, without a rewrite.
Keep the server you have. Layer Connect where it pays off, and leave the rest of the REST surface alone.
REST coexistence
Register Connect handlers next to ordinary Ktor routes. Keep REST until each endpoint earns a Connect replacement.
Learn moreConnect protocol, intact
JSON or binary codecs, Connect GET, structured errors, and client-streaming with envelope framing stay on the server.
Learn moreReact + Kotlin/Ktor
Connect-ES in front, Connect-Ktor in back, one .proto module. A natural split when the stack is already typed that way.
Learn moreDocumentation
Start where you need.
Introduction
What it is, who it is for, and how it relates to Connect-Kotlin.
Getting started
Dependencies, code generation, and a handler beside REST.
Docs
Introduction, getting started, plugins, and conformance notes.
Plugins
Serialization, Connect GET, limits, compression, protovalidate.
Code generator
protoc-gen-connect-ktor route interfaces from .proto services.
Known limitations
gRPC, streaming compression, and engine gaps — stated up front.
Ship Connect on the Ktor you already run.
Wire a handler, keep your REST routes, and grow the Connect surface one RPC at a time.