Skip to content

Clarify bom usage for creating MCP servers #464

@wjglerum

Description

@wjglerum

I'm a bit confused on which bom we should use for projects using the quarkus mcp server extensions.

The docs have recently been updated to show that we can use a bom, see #450

There's also a bom available from the quarkus platform. This bom is also recommended by the quarkus update command:

[INFO] Suggested Quarkus platform BOM updates:
[INFO]  +       [io.quarkus.platform:quarkus-mcp-server-bom:pom:3.27.0]
[INFO] 
[INFO] Suggested extensions updates for 'io.quarkus.platform:quarkus-mcp-server-bom':
[INFO]  -       io.quarkiverse.mcp:quarkus-mcp-server-stdio:[1.7.0 -> managed]

However after accepting the changes they do not actually get applied to the project 🤷

I did try changing it manually and that did work:

            <dependency>
                <groupId>${quarkus.platform.group-id}</groupId>
                <artifactId>quarkus-mcp-server-bom</artifactId>
                <version>${quarkus.platform.version}</version>
                <type>pom</type>
                <scope>import</scope>
            </dependency>

This is also what's used when you generate a new project on code.quarkus.io:
https://code.quarkus.io/?e=io.quarkiverse.mcp%3Aquarkus-mcp-server-stdio&extension-search=mcp%20server

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions