Model Context Protocol (MCP) can connect OpenSearch and AI tools in three different ways: an external AI client can call OpenSearch tools; an OpenSearch agent can call tools on an external MCP server; or an AI client can call the MCP endpoint hosted by OpenSearch ML Commons. Choose the path by deciding which side should initiate the tool call—then check that path’s transport, version, and security requirements.
Choose the MCP direction that fits your setup
“OpenSearch with MCP” can mean exposing OpenSearch to an AI assistant or letting an OpenSearch agent use tools elsewhere. These are complementary integrations, not interchangeable names for one server. OpenSearch also has an in-cluster MCP endpoint, which is a separate way to expose tools.
| Integration | Who calls the tools? | Where the MCP server runs | Transport documented | Version context |
|---|---|---|---|---|
| OpenSearch MCP Server | An external MCP-compatible AI client calls OpenSearch tools. | As the separate OpenSearch MCP Server project. | Local stdio and remote streaming transports; consult the project documentation for the deployment-specific setup. | A separately documented Python project; the ML Commons 3.0 and 3.3 version introductions do not apply to it. |
| ML Commons external MCP connector | An OpenSearch agent calls tools on an external MCP server. | Outside the OpenSearch cluster. | SSE or Streamable HTTP; stdio is not supported. | Documented as introduced in OpenSearch 3.0. |
| ML Commons MCP server endpoint | An external MCP client calls tools exposed by OpenSearch. | At the OpenSearch ML Commons endpoint. | Streamable HTTP. | The endpoint is documented as introduced in OpenSearch 3.3; the tool-registration API is documented as introduced in 3.0. |
For a client that needs to search or explore OpenSearch data, start with the first or third row. For an OpenSearch agent that needs to combine OpenSearch work with an external service’s tools, use the connector in the second row.
Let an external AI client query OpenSearch
The OpenSearch MCP Server translates MCP tool calls into OpenSearch REST API calls. Its documented core tools cover listing indices, retrieving mappings, searching, checking cluster health, counting documents, explaining queries, multi-search, retrieving shard information, and making generic OpenSearch API calls. Additional tool categories can be enabled.
Recommended Free Tools
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
The server is intended for MCP-compatible clients, including desktop and coding assistants. Its documentation lists self-managed OpenSearch, Amazon OpenSearch Service, and Amazon OpenSearch Serverless as compatible environments. Compatibility does not by itself establish availability in every region or configuration.
Choose the connection style and credentials
The project documents stdio for local desktop-client integrations and streaming transports for remote deployments. Authentication options include basic authentication, AWS IAM roles, AWS profiles, header-based authentication, mutual TLS, and anonymous access. These are available approaches, not a claim that every method is enabled by default. Select the method appropriate to your deployment and grant only the access the client needs; anonymous access should not be treated as a safe default.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
The official Python repository documents installation of opensearch-mcp-server-py with pip and a zero-configuration mode in which the client supplies the OpenSearch endpoint and authentication details with tool calls. Those details are implementation-specific and may change, so use the repository’s current setup instructions rather than assuming a command or configuration is universal: OpenSearch MCP Server Python project.
Let an OpenSearch agent call an external MCP server
The ML Commons external MCP connector reverses the direction: an OpenSearch agent uses tools hosted by an MCP server outside the cluster. OpenSearch documentation marks this connector as introduced in version 3.0. The cluster must be able to reach the external server, and the connector supports SSE and Streamable HTTP—not stdio. See the ML Commons MCP connector documentation.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Prepare the cluster and trust the endpoint
Before creating the connector, enable the MCP connector and configure trusted endpoint patterns. The setting names are plugins.ml_commons.mcp_connector_enabled and plugins.ml_commons.trusted_connector_endpoints_regex. Match the trusted patterns to the intended MCP endpoints, and verify network connectivity from the cluster; a syntactically valid connector cannot call a server it cannot reach.
Register the connector, model, and agent
The documented workflow is to create an MCP connector, register an externally hosted model, register an agent that includes the MCP connector and tool filters, then execute the agent. For fixed-flow agent types, first discover the external server’s tool names and schemas with the List Connector MCP Tools API, then configure the agent with the tools it should use. Tool filters can restrict which external tools are available. If multiple connectors expose the same tool name, connector order can determine which one supplies that tool, so avoid ambiguous names or configure order deliberately.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Expose the in-cluster ML Commons MCP endpoint
If you want an external client to call tools served from OpenSearch itself, ML Commons also documents an MCP endpoint at /_plugins/_ml/mcp. It uses Streamable HTTP, can list tools and invoke them through JSON-RPC, and is enabled with plugins.ml_commons.mcp_server_enabled. OpenSearch documentation marks this endpoint as introduced in version 3.3. The separate MCP tool-registration API—used to define tool names, types, descriptions, parameters, and input schemas—is documented as introduced in version 3.0. Consult the ML Commons MCP server documentation for endpoint and API details.
This endpoint is not the external OpenSearch MCP Server project. Choose it when the ML Commons-hosted endpoint and Streamable HTTP fit your client and cluster; choose the external project when its client integration and deployment options better fit your setup.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Check transport, version, and security before connecting
- Transport: Confirm that client and server support the same transport. The external OpenSearch MCP Server documents local stdio and remote streaming; the external connector accepts SSE or Streamable HTTP and explicitly excludes stdio; the in-cluster endpoint uses Streamable HTTP.
- Version: Check the target OpenSearch version and the specific feature documentation. The 3.0 label applies to the external connector and tool-registration API; 3.3 applies to the in-cluster MCP server endpoint. Neither label describes the separately documented Python server project.
- Network path: For an external connector, ensure the cluster can reach the MCP server. For a client connecting to OpenSearch, ensure the client can reach the chosen server or endpoint.
- Permissions and scope: Set credentials deliberately, configure trusted connector endpoint patterns where applicable, and expose only the tools the client or agent needs. A tool that can issue generic API calls may have broader consequences than a narrowly scoped search tool.
- Changing documentation: OpenSearch documentation uses rolling
/latest/URLs. Verify current settings, supported transports, authentication options, and deployment compatibility against the documentation for the version you run.
What MCP changes—and what it does not establish
MCP provides a standard tool interface between a client or agent and a server. In these OpenSearch integrations, tool calls ultimately operate through OpenSearch APIs or invoke tools provided by an external MCP server. The documentation describes capabilities and setup; it does not establish a particular performance gain, latency improvement, or productivity percentage. Those outcomes depend on the cluster, model, tools, permissions, and workload.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
