ESA MCP Server

Created By
masseatera year ago
mcp server for esa.io
Overview

What is ESA MCP Server?

ESA MCP Server is a Model Context Protocol (MCP) server designed to interact with the esa.io API, allowing users to perform various operations related to articles and user information.

How to use ESA MCP Server?

To use the ESA MCP Server, you can run it directly from the JavaScript Registry (JSR) without cloning the repository. Ensure you have Deno installed and set up the required environment variables.

Key features of ESA MCP Server?

  • Retrieve user information from esa.io
  • Fetch a list of articles
  • Get details of specific articles
  • Create, update, and delete articles

Use cases of ESA MCP Server?

  1. Managing articles for a team on esa.io
  2. Automating the retrieval of user data
  3. Integrating esa.io functionalities into other applications

FAQ from ESA MCP Server?

  • What is required to run the ESA MCP Server?

You need Deno v2.0 or later and an internet connection.

  • Is there a way to run it locally?

Yes, you can clone the repository and run it locally after setting up the environment variables.

  • What permissions does the server require?

The server requires permissions to access environment variables, network access to the esa.io API, and read access for local files.

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