Custom MCP Servers

Created By
tiagodreada year ago
Custom MCP servers
Overview

what is Custom MCP Servers?

Custom MCP Servers is a collection of custom Model Context Protocol servers designed to facilitate interaction with cursor or Visual Studio Code (VSCode).

how to use Custom MCP Servers?

To use Custom MCP Servers, clone the repository from GitHub and follow the setup instructions provided in the documentation to configure the servers for your development environment.

key features of Custom MCP Servers?

  • Customizable server configurations for different development needs.
  • Integration with cursor and VSCode for enhanced coding experience.
  • Open-source and community-driven development.

use cases of Custom MCP Servers?

  1. Setting up a personalized development environment with custom server settings.
  2. Enhancing productivity in coding tasks through tailored server interactions.
  3. Collaborating with teams using shared custom server configurations.

FAQ from Custom MCP Servers?

  • What is the purpose of Custom MCP Servers?

The purpose is to provide developers with customizable servers that improve their interaction with coding tools like cursor and VSCode.

  • Is there any documentation available?

Yes! Documentation is available in the GitHub repository to guide users through setup and usage.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can submit pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tiagodread
Star
0
Language
Shell
License
-

Recommend Servers

View All
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.

18 minutes ago