Use Elasticsearch from Claude
Add the Elasticsearch connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Elasticsearch once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Elasticsearch connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Elasticsearch connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Elasticsearch indexes and searches large volumes of data in near real time, powering everything from log analysis to full-text search. An engineering Space in type.com can ask Claude to check cluster health, inspect an index's field mappings, or run a filtered query, so debugging a search or data issue happens inside the same thread as the rest of the investigation.
Connect Elasticsearch once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Ping the cluster first to confirm it's reachable and healthy before digging into a specific index or query problem.
Ping our Elasticsearch cluster and tell me if it's responding normally.
Pull an index's schema to see its field types and mappings before building a query against unfamiliar data.
Get the schema for the orders-2026 index so I know what fields are available to query.
Query an index with a time range and filter to pull the documents behind a reported spike, instead of writing raw queries by hand.
Query the logs-prod index for error-level entries from the last hour and summarize the top error types.
Returns the field types and mappings for a specific Elasticsearch index.
Lists available indices in the cluster, with optional filtering by name pattern or health status.
Checks whether the Elasticsearch cluster is reachable and reports its basic health.
Searches an index with filters, time ranges, and pagination to return matching documents.
Elasticsearch provides REST APIs for indexing, search, aggregations, mappings, ingest pipelines, aliases, templates, snapshots, tasks, cluster health, security, connectors, and machine-learning/search workflows. Official clients are available across major languages, and integrations typically use Elastic Cloud credentials, API keys, or service tokens.
Yes. Once an Elasticsearch connection is shared with a Space, the agent can list indices, inspect schemas, and run filtered queries from any thread.
Elasticsearch supports an API key or basic auth. An admin adds the credential once when creating the connection, then controls which Spaces can use it.
Yes. An automation can ping the cluster or query an index periodically and post results to a channel, useful for a lightweight health check.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect GTmetrix to Claude in type.com to check test locations, review browser options, and clean up old reports from a shared dev thread.
Connect Hashnode to Claude in type.com to reply to post comments, extend documentation projects, and configure custom domains from a thread.
Connect Here to Claude in type.com to browse places, plan fleet routes, and convert coordinates from a shared thread.
Connect Honeybadger to Claude in type.com to report deployments, log exceptions, and send check-ins from a shared engineering thread.