MCP servers · cloudcorprecords

embedbase: MCP server and CLI for vector collections

An MCP server and command-line client for creating vector collections, adding documents and running nearest-match queries against a Chroma-compatible HTTP service.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

embedbase lets an agent, or a person at a terminal, manage vector collections: create them, fill them with documents, and query them for the closest matches. It talks to a Chroma-compatible HTTP service over its v2 REST API, so the embedding store runs as a separate process and the tool stays a thin client. Collections are addressed by name, and the client resolves each name to its server id before calling the document endpoints.

The MCP server exposes tools to list, create, peek at, inspect, count, rename, re-tag and delete collections, and to add, query, fetch, update and delete documents. Querying returns nearest neighbours. The same binary also works as a CLI, which exits with 0 on success, 1 when a service call fails, and 2 for usage errors. Service failures are returned as tool errors that include the HTTP status, so results are not invented when the service fails.

The server is started with the mcp subcommand over stdio. The service location is set with CHROMA_URL or EMBEDBASE_URL, and defaults to http://localhost:8000 when neither is set. A container image is also available; it starts the MCP server by default, and passing CLI arguments runs it as a CLI instead. The client core accepts an injectable fetch function, so its tests run without a live server. The project is released under the MIT license.

Limitations and requirements

Requires a running Chroma-compatible HTTP service that exposes the v2 REST API. The service address is taken from CHROMA_URL or EMBEDBASE_URL, or assumed to be http://localhost:8000 if neither is set.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/embedbase

    Vector collections and document search backed by a Chroma HTTP service.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026