MCP Server Template for Cursor IDE

Created By
MyBlockcitiesa year ago
Overview

What is MCP Server Template for Cursor IDE?

MCP Server Template for Cursor IDE is a simple template designed for creating custom tools for Cursor IDE using Model Context Protocol (MCP). It allows users to create their own repositories, modify tools, and connect them to Cursor IDE.

How to use MCP Server Template?

To use the MCP Server Template, you can deploy it to Heroku, configure it in Cursor IDE, and test your agent's mood. You can also run the server using Docker or a traditional Python setup.

Key features of MCP Server Template?

  • Easy deployment to Heroku with a single click.
  • Supports Docker for containerized deployment.
  • Traditional Python setup for flexibility.
  • Customizable environment variables for server configuration.

Use cases of MCP Server Template?

  1. Creating custom tools for Cursor IDE.
  2. Testing agent responses in Cursor IDE.
  3. Deploying server applications quickly using Heroku.

FAQ from MCP Server Template?

  • Can I run the server locally?

Yes! You can run the server using Docker or a traditional Python setup.

  • Is there a way to customize the server settings?

Yes! You can set various environment variables in the .env file to customize the server settings.

  • How do I test the server after deployment?

You can test the server by accessing the SSE endpoint or using the provided curl command.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MyBlockcities
Star
-
Language
-
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.

8 hours ago