Express MCP Server

Created By
jhgaylora year ago
An MCP server providing tools to extract text from things
Overview

what is Express MCP Server?

Express MCP Server is a stateless Model Context Protocol (MCP) server built with Express and TypeScript, designed to provide tools for extracting text from various sources.

how to use Express MCP Server?

To use the Express MCP Server, clone the repository, install the dependencies, and run the server. You can interact with the server by sending JSON-RPC requests to the /mcp endpoint.

key features of Express MCP Server?

  • Stateless MCP server implementation with modern Streamable HTTP transport
  • TypeScript for type safety
  • Express.js for HTTP handling
  • Simple echo endpoint with MCP components for resource, tool, and prompt

use cases of Express MCP Server?

  1. Extracting text from user inputs and returning it as a resource.
  2. Implementing tools that require echoing messages back to users.
  3. Creating user prompts based on provided messages.

FAQ from Express MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized way for LLMs to interact with external data and functionality.

  • How do I install the server?

Clone the repository and run npm install to install the dependencies.

  • Can I run this server in development mode?

Yes! You can run the server in development mode with auto-reloading using npm run dev.

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

a day ago