EigenLayer MCP Server built on Next.js

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is EigenLayer MCP Server?

EigenLayer MCP Server is a server built on Next.js that provides EigenLayer documentation to AI assistants like Claude via the Model Context Protocol (MCP).

how to use EigenLayer MCP Server?

To use the EigenLayer MCP Server, you can run it locally or deploy it as a serverless function on Vercel. You can add the live URL to Claude and test it with queries related to EigenLayer's functionalities.

key features of EigenLayer MCP Server?

  • Provides EigenLayer documentation to AI assistants.
  • Can run as a standalone server or as a serverless function.
  • Allows testing with a sample client and MCP Inspector.

use cases of EigenLayer MCP Server?

  1. Integrating EigenLayer documentation with AI assistants for easy access.
  2. Testing EigenLayer functionalities in a local development environment.
  3. Facilitating queries about EigenLayer's restaking mechanism.

FAQ from EigenLayer MCP Server?

  • Is EigenLayer MCP Server production-ready?

No, it is under active development and should only be used for testing purposes.

  • How can I report security vulnerabilities?

Please report security vulnerabilities to security@eigenlabs.org and not via GitHub Issues.

  • What technologies does EigenLayer MCP Server use?

It is built using Next.js and TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago
Crevio

a day ago