OpenSearch MCP integration
Search, inspect, and manage OpenSearch indices and documents over the REST API.
Sign in, add OpenSearch in Apps, then choose the account your AI can use.
Tools
| Name | Description |
|---|---|
validate_connectionValidate OpenSearch credentials with a low-impact cluster info request. | Validate OpenSearch credentials with a low-impact cluster info request. |
list_indicesList OpenSearch indices using the cat indices JSON endpoint. | List OpenSearch indices using the cat indices JSON endpoint. |
get_indexGet OpenSearch index settings, mappings, and aliases for one index. | Get OpenSearch index settings, mappings, and aliases for one index. |
create_indexCreate an OpenSearch index with optional settings, mappings, and aliases. | Create an OpenSearch index with optional settings, mappings, and aliases. |
delete_indexDelete one OpenSearch index. Requires the exact index name to be repeated for confirmation. | Delete one OpenSearch index. Requires the exact index name to be repeated for confirmation. |
search_documentsRun an OpenSearch Query DSL search against an index or all indices. | Run an OpenSearch Query DSL search against an index or all indices. |
index_documentCreate or replace a document in an OpenSearch index. | Create or replace a document in an OpenSearch index. |
update_documentPartially update a document by ID using the OpenSearch update API. | Partially update a document by ID using the OpenSearch update API. |
get_documentRetrieve one OpenSearch document by index and document ID. | Retrieve one OpenSearch document by index and document ID. |
delete_documentDelete one OpenSearch document. Requires the exact document ID to be repeated for confirmation. | Delete one OpenSearch document. Requires the exact document ID to be repeated for confirmation. |
custom_api_callMake a guarded custom call to the configured OpenSearch cluster origin. | Make a guarded custom call to the configured OpenSearch cluster origin. |
Triggers
| Name | Description |
|---|---|
search_results_changedPolls an OpenSearch query and triggers when the top result IDs or versions change. | Polls an OpenSearch query and triggers when the top result IDs or versions change. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('opensearch', 'validate_connection', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'opensearch',
input: { /* ... */ },
})Related Integrations
Works well with
Frequently Asked Questions
Is there a OpenSearch MCP server through Weavz?
Yes. Add the OpenSearch integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 11 OpenSearch actions.
What can an AI agent do with OpenSearch?
Available actions include Validate Connection, List Indices, Get Index, Create Index, Delete Index, and more. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect OpenSearch to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add OpenSearch, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use OpenSearch through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does OpenSearch require?
The catalog lists custom credentials for OpenSearch. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.
How do I review sensitive OpenSearch actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to OpenSearch?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
What OpenSearch triggers are available?
The catalog lists 1 triggers, including Search Results Changed. Configure the trigger and your event handler before using incoming events to start work.
Connect OpenSearch in minutes
Get 20,000 free action executions every month. No credit card required.