CopilotHub
SearchPromptsInstructionsAgentsToolsMCPs
  1. Home
  2. Instructions
  3. Quarkus MCP Server
Back to Instructions

Quarkus MCP Server

Coding standards for quarkus mcp server sse.instructions

java
0 downloads
73 views
0

Tags

testing
best-practices

Related Instructions

View all →

Spring Boot 2 → 3 Migration Guide (Jakarta EE)

**/*.java

Production-safe step-by-step playbook to migrate Spring Boot 2.x to 3.x with Jakarta EE, Java 17, Spring Security 6, and Hibernate 6

java
spring-boot
spring-boot
java
+5
1
845

Python Docstring Standards

*.py

Write clear and consistent Python docstrings

python
python
documentation
+1
1
117

TypeScript Error Handling

*.ts

Comprehensive error handling patterns for TypeScript applications

typescript
typescript
error-handling
+1
0
101

React Component Best Practices

*.tsx

Guidelines for creating maintainable and performant React components

typescript
react
react
typescript
+2
0
116

WordPress Development — Copilot Instructions

Coding standards for wordpress.instructions

typescript
testing
security
+5
1
185

VueJS 3 Development Instructions

Coding standards for vuejs3.instructions

typescript
react
testing
security
+6
0
157
Browse More Instructions

CopilotHub

A curated collection of prompts, instructions, agents, and tools for AI-powered development.

Quick Links

  • Prompts
  • Instructions
  • Agents
  • Tools
  • MCPs
  • Search

Browse by Category

  • Code Generation
  • Debugging
  • Documentation
  • Refactoring
  • Testing
  • Security

Legal

  • Guidelines
  • About
  • Privacy Policy
  • Terms of Service

Community

GitHub

© 2026 CopilotHub.

Quarkus MCP Server

Build MCP servers with Java 21, Quarkus, and HTTP SSE transport.

Stack

  • Java 21 with Quarkus Framework
  • MCP Server Extension: mcp-server-sse
  • CDI for dependency injection
  • MCP Endpoint: http://localhost:8080/mcp/sse

Quick Start

bash
quarkus create app --no-code -x rest-client-jackson,qute,mcp-server-sse your-domain-mcp-server

Structure

  • Use standard Java naming conventions (PascalCase classes, camelCase methods)
  • Organize in packages: model, repository, service, mcp
  • Use Record types for immutable data models
  • State management for immutable data must be managed by repository layer
  • Add Javadoc for public methods

MCP Tools

  • Must be public methods in @ApplicationScoped CDI beans
  • Use @Tool(name="tool_name", description="clear description")
  • Never return null - return error messages instead
  • Always validate parameters and handle errors gracefully

Architecture

  • Separate concerns: MCP tools → Service layer → Repository
  • Use @Inject for dependency injection
  • Make data operations thread-safe
  • Use Optional<T> to avoid null pointer exceptions

Common Issues

  • Don't put business logic in MCP tools (use service layer)
  • Don't throw exceptions from tools (return error strings)
  • Don't forget to validate input parameters
  • Test with edge cases (null, empty inputs)