WarpSearch

io.github.warpsearchioPublished by GitHub account warpsearchiov07c29b2c5d6b306682ac528fc1111fc301ce64f4Updated Oct 30, 2026

Serverless hybrid search: full-text, vector and faceted search, in SQL, ES DSL, Solr and more.

VerifiedStreamable HTTPWeb executableDatabasesKnowledge & MemoryData & Analytics

Overview

AI-generated overview

WarpSearch is a remote serverless hybrid search service that lets an assistant index JSON documents and query them in SQL, Elasticsearch DSL, Solr, Lucene…

What you can do
  • Register an account and claim an API key for the user's organization email
  • Index JSON documents into collections and search them with full-text (BM25), vector and faceted queries
  • Run analytics such as facets, metrics and date histograms
  • Retrieve graph neighborhoods and shortest paths
  • Query in SQL (MySQL/PostgreSQL dialects), Elasticsearch/OpenSearch DSL, Solr, Lucene, Grafana, LogQL or the native language
When to use it
Useful when an assistant needs a hosted search backend for an application, log and event analytics, or searchable memory over JSON documents, and the user is willing to create a WarpSearch account.
Requirements
A remote endpoint at api.warpsearch.io over streamable HTTP; no local runtime. A WarpSearch API key (ws_live_...) sent in the Authorization header as a Bearer token. Without a key only register and claim_registration are available, and registration needs a work email address on the user's own organization domain.
Before you install
The server asks for the user's email address and sends them mail; only use an address the user explicitly provided with consent. The API key is returned once by claim_registration and grants access to the account's data, so it should be stored and shared carefully. Indexing and querying act on the user's collections, and documents sent to the service leave the local machine.

Installation

In SourceWeft

  1. Open WarpSearch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.warpsearchio%2Fwarpsearch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "warpsearch": {
      "type": "http",
      "url": "https://api.warpsearch.io/mcp"
    }
  }
}

Tools

2

claim_registration

Claim registration

Check on a registration, and receive the API key once your user has approved it. Returns status: pending (not approved yet; ask your user to finish, then call again), approved (with api_key, shown only this once, and how to reconnect with it), denied, expired, or claimed (the key was already handed out).

Parametersclaim_tokenrequired

register

Register for WarpSearch

Ask WarpSearch for an account and an API key for your user. Use only an email address your user gave you for this, with their consent. The address must be a work address at your user's organization's own domain. Personal and free mailbox providers (gmail.com, outlook.com, hotmail.com, yahoo.com, icloud.com, proton.me, disposable addresses and the like) are refused with code personal_email during the public preview; ask your user for their work address instead of retrying. WarpSearch emails that address. Your user follows the link, creates the account if they have none, checks that the code matches the user_code you show them, and approves, choosing the organization and the role you get. Nothing is created until they approve, and the answer is the same whether or not the address already has an account. Returns user_code (show it to your user), claim_token (keep it secret; pass it to claim_registration), expires_at and next_steps. Each address gets at most 3 sign-up emails an hour.

Parametersnameroleagentemailrequired

Version history

1
  1. v07c29b2c5d6b306682ac528fc1111fc301ce64f4LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.