Quarkus Model Context Protocol (MCP) Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Quarkus Model Context Protocol (MCP) Server?

The Quarkus MCP Server is an implementation of the Model Context Protocol (MCP), which facilitates seamless integration between large language model (LLM) applications and external data sources and tools.

How to use Quarkus MCP Server?

To use the Quarkus MCP Server, follow these steps:

  1. Add the dependency to your POM file:
    <dependency>
        <groupId>io.quarkiverse.mcp</groupId>
        <artifactId>quarkus-mcp-server</artifactId>
        <version>${project-version}</version>
    </dependency>
    
  2. Implement server features using annotated business methods in a CDI bean.
  3. Run your Quarkus application.

Key features of Quarkus MCP Server?

  • Declarative API for easy implementation of MCP server features.
  • Support for HTTP/SSE transport.
  • Integration with various tools and resources through annotations.

Use cases of Quarkus MCP Server?

  1. Assisting in code generation and modification based on user prompts.
  2. Integrating external data sources for enhanced LLM capabilities.
  3. Facilitating real-time data processing and responses in applications.

FAQ from Quarkus MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol designed to enable integration between LLM applications and external data sources.

  • What transport methods are supported?

Currently, only HTTP/SSE transport is supported.

  • How can I contribute to the project?

Contributions are welcome! Please refer to the project's GitHub page for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

5 hours ago
Alloy

2 days ago