mcp-server-opensearch: An OpenSearch MCP Server

Created By
MCP-Mirrora year ago
Mirror of
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.
  • Supports asynchronous operations for efficient data handling.
  • Easy installation and configuration through command-line tools.

Use cases of mcp-server-opensearch?

  1. Building AI-powered applications that require context-aware memory management.
  2. Enhancing chat interfaces with memory capabilities.
  3. Creating custom AI workflows that leverage external data sources.

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.

  • 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 scalable data storage and retrieval.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
Apache-2.0 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.

8 hours ago