Grpc Mcp Bridge Kotlin

grpc-mcp-bridge-kotlin

Expose your existing gRPC services as MCP tools — and serve them natively from the JVM on Netty. Each proto method becomes a tool whose input schema is derived from its request descriptor; an incoming tool call is parsed into the proto request and dispatched to your handler in-process. No sidecar, no servlet container, no Spring in the core.

[](https://github.com/cgardev/grpc-mcp-bridge-kotlin/actions/workflows/ci.yml) [](https://central.sonatype.com/artifact/io.github.cgardev/mcp-grpc-bridge) [](LICENSE) [](https://kotlinlang.org) [](https://adoptium.net) [](#disclaimer)

> [!WARNING] > Alpha. This project is in early, active development. The public API, wire behaviour and > module layout may change without notice between releases, and it has not been hardened for > production use. Pin an exact version and review the release notes before upgrading. See the > [disclaimer](#disclaimer).

Why

MCP lets models call tools, and most JVM backends already expose their domain logic over gRPC. Hand-writing an MCP tool for each RPC — its JSON Schema, its argument parsing, its response serialisation — is repetitive and drifts from the proto definitions over time.

grpc-mcp-bridge-kotlin removes that boilerplate. It turns a gRPC service method into an MCP tool automatically, keeping the tool contract in lock-step with the proto, and serves the result over an embedded Netty HTTP transport — the same no-servlet, no-framework approach as connect-kotlin-server.

How it works

The bridge spans both directions:

• gRPC → MCP (exposure). [ProtoJsonSchema](project/lib-protobuf-jsonschema) converts the proto

request descriptor into a JSON Schema (draft 2020-12) that round-trips with com.google.protobuf.util.JsonFormat. That schema becomes the tool's inputSchema, so the model sees exactly the fields the proto declares.

• MCP → gRPC (invocation). When the model calls the tool, GrpcMcpToolFactory parses the JSON

arguments into the typed proto request, invokes the gRPC handler (a suspend function) in-process, and serialises the proto response back to JSON as the tool result.

The MCP runtime is the MCP Java SDK in its stateless mode — every request is a self-contained JSON-RPC exchange, which is the right model for a tool proxy — hosted on a small embedded Netty HTTP/1.1 server. Blocking dispatch runs on a virtual-thread executor off the event loop.

Features

• Automatic tool schemas: input schema generated from the proto descriptor; no hand-written JSON.
• In-process dispatch: tool calls invoke the gRPC handler directly — no gRPC network hop.
• No framework lock-in: the core modules have zero dependency on Spring or the Servlet API.

Netty is the HTTP server. An optional Spring Boot starter is provided for those who want it.

• Pluggable context propagation: a McpCallContextBridge hook lets you carry per-request state

(for example an authenticated principal published by an upstream proxy) into the gRPC handler.

• Faithful proto/JSON mapping: well-known types, oneof, maps, enums, 64-bit integers and

NaN/Infinity are all handled as JsonFormat does.

Requirements

• JDK 24+
• gRPC services generated with grpc-kotlin (any coroutine suspend method works as a tool target)

Installation

The modules are published to Maven Central under the io.github.cgardev group. While the project is in alpha, every commit on main is published as a release versioned by its short commit hash, so you can pin to an exact build; tagged releases publish a semantic version.

repositories {
    mavenCentral()
}

dependencies {
    // Replace  with a short commit SHA from main (or a release version once tagged).
    implementation("io.github.cgardev:mcp-grpc-bridge:")
    implementation("io.github.cgardev:mcp-server:")
    // Optional Spring Boot starter:
    // implementation("io.github.cgardev:mcp-grpc-bridge-spring-boot-autoconfigure:")
}

> [!WARNING] > Alpha. The public API and wire behaviour may change between commits without notice. Pin an > exact version and review changes before upgrading.

Quick start

Wrap your service methods as tools and host them — no Spring required:

import io.github.cgardev.library.mcp.grpc.bridge.GrpcMcpToolFactory
import io.github.cgardev.library.mcp.server.McpServerBuilder

fun main() {
    val service = CalculatorService()                 // a grpc-kotlin coroutine service
    val factory = GrpcMcpToolFactory()

    val tools = listOf(
        factory.create("add", "Add two numbers.", BinaryOp.getDefaultInstance(), service::add),
        factory.create("divide", "Divide a by b.", BinaryOp.getDefaultInstance(), service::divide),
    )

    val server = McpServerBuilder.build(
        port = 3000,
        serverName = "cgardev-calculator",
        serverVersion = "0.1.0",
        tools = tools,
    )
    server.start()                                    // binds Netty, serves MCP Streamable HTTP at /
    Runtime.getRuntime().addShutdownHook(Thread { server.close() })
}

With Spring Boot

The mcp-grpc-bridge-spring-boot-autoconfigure starter exposes a GrpcMcpToolFactory bean so you can inject it into your tool configuration; you still build and host the MCP server where you want:

dependencies {
    implementation("com.github.cgardev.grpc-mcp-bridge-kotlin:mcp-grpc-bridge-spring-boot-autoconfigure:")
}

@Configuration
class McpTools(private val factory: GrpcMcpToolFactory, private val service: CalculatorService) {
    @Bean
    fun calculatorTools() = listOf(
        factory.create("add", "Add two numbers.", BinaryOp.getDefaultInstance(), service::add),
    )
}

The bean backs off if you declare your own GrpcMcpToolFactory — useful for supplying a custom McpCallContextBridge.

Trying the example

The :project:app-server module exposes a demo CalculatorService over MCP:

./gradlew :project:app-server:run        # serves on http://localhost:3000/

# Initialize, then call a tool (MCP Streamable HTTP, single JSON-RPC request per POST):
curl -s localhost:3000/ \
  -H 'Content-Type: application/json' -H 'Accept: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"add","arguments":{"a":2,"b":3}}}'
# => the CalcResult serialised as JSON: {"value":5.0}

Project layout

project/lib-protobuf-jsonschema/                       Proto descriptor -> JSON Schema (draft 2020-12). Pure, no framework.
project/lib-mcp-server/                                Embedded Netty MCP Streamable HTTP server. Servlet-free, Spring-free.
project/lib-mcp-grpc-bridge/                            Turns gRPC methods into MCP tools (the bridge core).
project/lib-mcp-grpc-bridge-spring-boot-autoconfigure/ Optional Spring Boot starter (a GrpcMcpToolFactory bean).
project/app-server/                                    Runnable example: a gRPC CalculatorService exposed as MCP tools.
build-logic/                                           Gradle convention plugins.

Building

./gradlew build      # compile + test every module

Versioning & compatibility

During alpha the commit is the version: every commit on main is published to Maven Central under its short commit hash, and source, binary and wire behaviour may change between any two commits. Once the API settles the project will adopt semantic versioning with tagged releases. Pin an exact version and upgrade deliberately.

Publishing

Publishing goes to Maven Central under the io.github.cgardev group, through the Sonatype Central Portal:

• Every push to main publishes a release versioned by the short commit hash.
• Publishing a GitHub release publishes the tag's version.

Both sign the artifacts and promote the Central staging deployment automatically (publishing_type=automatic), so it is released to Maven Central once validation passes. The flow runs from [.github/workflows/publish.yml](.github/workflows/publish.yml) and requires the CENTRAL_USERNAME, CENTRAL_PASSWORD, SIGNING_KEY and SIGNING_PASSWORD repository secrets.

Disclaimer

This is alpha software, provided "as is", without warranty of any kind, express or implied. To the maximum extent permitted by applicable law, the authors and contributors shall not be liable for any claim, damages, data loss or other liability arising from, out of or in connection with the software or its use. You use it at your own risk. See Sections 7 and 8 of the [Apache License 2.0](LICENSE) for the full terms.

License

[Apache License 2.0](LICENSE). Not affiliated with or endorsed by the Model Context Protocol project, Anthropic, or the gRPC project.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: cgardev
• Source: cgardev/grpc-mcp-bridge-kotlin
• License: Apache-2.0
• Homepage: https://jitpack.io/#cgardev/grpc-mcp-bridge-kotlin

Install and usage instructions live in the source repository linked above.