mcp

Created By
meghanmurphy1a year ago
Python implementation of an Elasticsearch MCP server
Overview

what is MCP?

MCP is a Python implementation of an Elasticsearch MCP server designed to facilitate the management and configuration of Elasticsearch instances.

how to use MCP?

To use MCP, ensure you have Claude desktop installed and an instance of Elasticsearch running. Configure the .env file appropriately, then run the commands:

  • make add-claude-config
  • make run

key features of MCP?

  • Easy integration with Elasticsearch for configuration management.
  • Simple command-line interface for running and managing the server.
  • Supports configuration through environment variables.

use cases of MCP?

  1. Managing Elasticsearch configurations in a development environment.
  2. Automating the setup of Elasticsearch instances.
  3. Facilitating quick deployments of Elasticsearch servers.

FAQ from MCP?

  • What is required to run MCP?

You need Claude desktop and an instance of Elasticsearch running.

  • Is MCP open-source?

Yes, MCP is available on GitHub and can be freely used and modified.

  • How do I contribute to MCP?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
meghanmurphy1
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago