Servidor MCP para Claude Desktop

Created By
Bufigola year ago
Overview

What is the Custom MCP Server?

The Custom MCP Server is a Message Control Protocol (MCP) server designed for Claude Desktop, enabling interaction with the local system for various operations.

How to use the Custom MCP Server?

To use the Custom MCP Server, compile the project using Maven, run the server, and connect from Claude Desktop using the MCP protocol.

Key features of the Custom MCP Server?

  • Read and write files on the local system.
  • Perform network requests.
  • Connect to and query MySQL databases (optional).

Use cases of the Custom MCP Server?

  1. Automating file operations for applications.
  2. Making network requests to APIs.
  3. Interacting with databases for data retrieval and manipulation.

FAQ from the Custom MCP Server?

  • What are the requirements to run the server?

You need Java 17 or higher, Maven 3.6 or higher, and optionally a MySQL Server if database functionality is used.

  • How do I compile and run the server?

Compile using mvn clean package and run with java -jar target/servidor-mcp-1.0-SNAPSHOT.jar.

  • Is there any security consideration?

Yes, run the server with minimal permissions and implement authentication for production use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Bufigol
Star
0
Language
Java
License
View license

Recommend Servers

View All
Payai X402 Tools

6 hours 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.

a day ago