MCP Eagle Server

Created By
olegshilina year ago
MCP server for Eagle app
Overview

what is MCP Eagle Server?

MCP Eagle Server is a Model Context Protocol (MCP) server designed for interfacing with the Eagle app, enabling seamless communication and functionality.

how to use MCP Eagle Server?

To use MCP Eagle Server, follow these steps:

  1. Install dependencies using npm install.
  2. Build the server with npm run build.
  3. Run the server using npm start. Additionally, configure it with Claude Desktop by adding the server details to the configuration file.

key features of MCP Eagle Server?

  • Facilitates communication between the Eagle app and other services.
  • Provides a command to check the connection status of the Eagle app.
  • Easy setup and integration with existing applications.

use cases of MCP Eagle Server?

  1. Integrating the Eagle app with other applications for enhanced functionality.
  2. Monitoring the connection status of the Eagle app in real-time.
  3. Building custom applications that require interaction with the Eagle app.

FAQ from MCP Eagle Server?

  • What is the purpose of MCP Eagle Server?

It serves as a bridge for communication between the Eagle app and other services, enhancing its capabilities.

  • Is there a graphical interface for MCP Eagle Server?

No, it is primarily a backend server that requires configuration through code.

  • Can I use MCP Eagle Server with other applications?

Yes, it can be integrated with various applications that support the Model Context Protocol.

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

17 hours ago