MCP Sample Java Application

Created By
Saularch97a year ago
Sample of an MCP server using Spring AI with Java
Overview

What is MCP Sample Java Application?

MCP Sample Java Application is a minimal Spring Boot application that implements an MCP (Model Controller Provider) server using Spring AI. It serves as an external MCP server for client applications.

How to use MCP Sample Java Application?

To use the application, clone the project from GitHub, build it using Maven, and configure your client to connect to the server.

Key features of MCP Sample Java Application?

  • Implements an MCP server using Spring AI.
  • Easy to set up and configure for client applications.
  • Built with modern Java technologies (Java 21 and Maven).

Use cases of MCP Sample Java Application?

  1. Serving as a backend for AI-driven applications.
  2. Integrating with various client applications like Cursor, ClaudeDesktop, and Vscode.
  3. Providing a scalable server solution for model-controller architecture.

FAQ from MCP Sample Java Application?

  • What are the requirements to run this application?

You need Java 21 and Maven 3.8+ to build and run the application.

  • How do I configure the client to connect to the server?

You need to insert the provided JSON configuration into your client application, replacing <PATH_TO_YOUR_PROJECT> with the actual path to your project directory.

  • Where can I find the project?

The project is available on GitHub at https://github.com/Saularch97/mcp-java-sample.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Saularch97
Star
0
Language
Java
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago