mcp-on-vercel

Created By
xaricala year ago
MCP Server on Vercel template
Overview

what is mcp-on-vercel?

MCP-on-Vercel is a template Model Context Protocol (MCP) server designed for easy deployment on Vercel, allowing developers to set up and run their own MCP servers.

how to use mcp-on-vercel?

To use mcp-on-vercel, clone the repository, install the necessary dependencies, and run the development server using Vercel CLI. You can also deploy it directly to Vercel with a single click.

key features of mcp-on-vercel?

  • Easy deployment to Vercel
  • Supports Server-Sent Events (SSE) and streamable HTTP transports
  • Customizable server configuration through TypeScript
  • Integration with Redis or Upstash databases

use cases of mcp-on-vercel?

  1. Setting up a custom MCP server for real-time applications.
  2. Testing and developing applications that require server-sent events.
  3. Deploying scalable applications on Vercel with minimal setup.

FAQ from mcp-on-vercel?

  • What is the purpose of this template?

This template serves as a starting point for developers to create and deploy their own MCP servers on Vercel easily.

  • Do I need to configure a database?

Yes, a Redis or Upstash database is required to connect to the project.

  • Can I customize the server?

Absolutely! You can update the api/server.ts file with your tools, prompts, and resources.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xarical
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Voyei

3 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.

13 hours ago