mcp-server-opensearch: An OpenSearch MCP Server

Created By
ibrooksSDXa year ago
Overview

What is mcp-server-opensearch?

The mcp-server-opensearch is an implementation of a Model Context Protocol (MCP) server designed to work with OpenSearch, a distributed search and analytics engine. It serves as a semantic memory layer that allows for the storage and retrieval of memories in the OpenSearch database.

How to use mcp-server-opensearch?

To use the mcp-server-opensearch, you can install it via Smithery or run it directly using the uv command. Configuration is done through a JSON file or environment variables to connect to your OpenSearch instance.

Key features of mcp-server-opensearch?

  • Seamless integration with OpenSearch for memory storage and retrieval.
  • Ability to run as a server for LLM applications.
  • Supports configuration through environment variables and JSON files.

Use cases of mcp-server-opensearch?

  1. Building AI-powered IDEs that require memory management.
  2. Enhancing chat interfaces with contextual memory.
  3. Creating custom AI workflows that need to store and retrieve data efficiently.

FAQ from mcp-server-opensearch?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that facilitates the integration of LLM applications with external data sources and tools.

  • How do I install mcp-server-opensearch?

You can install it using the Smithery CLI or run it directly with the uv command.

  • What is OpenSearch?

OpenSearch is a distributed search and analytics engine that allows for powerful data querying and analysis.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ibrooksSDX
Star
-
Language
-
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)

a day ago