Embedbase

io.github.CloudCorpRecords由 GitHub 账号 CloudCorpRecords 发布v0.1.0更新于 Nov 7, 2026

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

已验证STDIO仅桌面数据库知识与记忆

概览

AI 生成的概览

面向 Chroma 兼容向量服务的轻量 stdio MCP 客户端，让助手创建集合、写入文档并进行最近邻检索。

可以做什么
  • 列出、创建、查看、重命名和删除向量集合，支持分页与计数
  • 预览集合中的文档，读取集合元数据与配置
  • 添加带元数据和 id 的文档，并更新已有记录
  • 按查询文本做最近邻检索，并按 id 或过滤条件获取、删除文档
适用场景
当你已经运行了 Chroma 兼容的向量服务，并希望助手直接管理其中的集合与文档时适用，例如搭建或查看小型向量库、批量写入文档、执行相似度查询而无需手写 API 调用。
运行要求
通过 npx 或 Docker 镜像在本地运行；需要一个可访问的 Chroma 兼容 HTTP 服务，通过 CHROMA_URL 或 EMBEDBASE_URL 指定（默认 API 密钥。
安装前请注意
工具可创建、重命名、更新和删除集合与文档，包括按过滤条件批量删除，改动会直接作用于线上向量库。请只连接你确实要修改的服务，并注意文档文本与元数据会发送到该服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Embedbase，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

embedbase

embedbase gives an agent — or you, at a terminal — a tidy way to work with vector collections: create them, fill them with documents, and query them for the closest matches. It speaks to a Chroma-compatible HTTP service over its v2 REST API, so the embedding store stays a separate process and this tool stays a thin, testable client.

Point it at a running service with CHROMA_URL or EMBEDBASE_URL (without either, it assumes http://localhost:8000). Collections are addressed by name at the MCP and CLI layers; internally the client resolves each name to its server id before calling the id-scoped document endpoints, exactly as the REST API requires.

Install

bash
npx @reneturcios/embedbase list

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/embedbase

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash
# List collections (pagination is optional)embedbase list --limit 20 --offset 0
# Inspect one collection, or count its recordsembedbase info notesembedbase count notes
# Create a collectionembedbase create notes
# Start the MCP serverembedbase mcp
embedbase --version

Exit codes: 0 on success, 1 when the service call fails (the error includes the HTTP status), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/embedbase mcp

MCP client configuration:

json
{  "mcpServers": {    "embedbase": {      "command": "npx",      "args": ["-y", "@reneturcios/embedbase", "mcp"],      "env": { "CHROMA_URL": "http://localhost:8000" }    }  }}

Tools

All tools take collection_name (string) unless noted. Optional parameters are omitted from the request when not supplied.

ToolRequiredOptionalPurpose
chroma_list_collections—limit, offset (integers)List collections with pagination.
chroma_create_collectioncollection_namemetadata (object), embedding_function_name (string)Create a collection.
chroma_peek_collectioncollection_namelimit (integer)Preview documents in a collection.
chroma_get_collection_infocollection_name—Collection metadata and configuration.
chroma_get_collection_countcollection_name—Number of records in a collection.
chroma_modify_collectioncollection_namenew_name, new_metadataRename or re-tag a collection.
chroma_delete_collectioncollection_name—Delete a collection and its records.
chroma_add_documentscollection_name, documents (string array)metadatas, idsAdd documents; ids are generated deterministically when omitted.
chroma_query_documentscollection_name, query_texts (string array)n_results, where, where_document, includeNearest-neighbour query.
chroma_get_documentscollection_nameids, where, limit, offset, includeFetch documents by id or filter.
chroma_update_documentscollection_name, idsdocuments, metadatas, embeddingsUpdate existing records.
chroma_delete_documentscollection_nameids, whereDelete records by id or filter.

Requests go to the v2 tenant/database paths (/api/v2/tenants/default_tenant/databases/default_database/collections...). Service errors come back as tool errors carrying the HTTP status — results are never invented.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, fake fetch only, no live servicenpm run dev     # run the CLI from source via tsx

The client core sits behind an injectable fetch function, which is what the test suite drives: URL construction, request bodies, id resolution, count unwrapping, and error surfacing are all covered without a running server.

License

MIT — see LICENSE.

来源：README.md，提交 e555a07

工具

12

chroma_list_collections

List collections in the database with optional pagination.

输入参数limitoffset

chroma_create_collection

Create a new collection with optional metadata and embedding function.

输入参数metadatacollection_name必填embedding_function_name

chroma_peek_collection

Return a preview of documents stored in a collection.

输入参数limitcollection_name必填

chroma_get_collection_info

Get metadata and configuration details for a collection.

输入参数collection_name必填

chroma_get_collection_count

Get the number of records stored in a collection.

输入参数collection_name必填

chroma_modify_collection

Rename a collection or replace its metadata.

输入参数new_namenew_metadatacollection_name必填

chroma_delete_collection

Delete a collection and all of its records.

输入参数collection_name必填

chroma_add_documents

Add documents with optional metadata and ids to a collection.

输入参数idsdocuments必填metadatascollection_name必填

chroma_query_documents

Query a collection for documents nearest to the given query texts.

输入参数whereincluden_resultsquery_texts必填where_documentcollection_name必填

chroma_get_documents

Retrieve documents from a collection by ids or filter.

输入参数idslimitwhereoffsetincludecollection_name必填

chroma_update_documents

Update documents, metadata, or embeddings for existing ids in a collection.

输入参数ids必填documentsmetadatasembeddingscollection_name必填

chroma_delete_documents

Delete documents from a collection by ids or filter.

输入参数idswherecollection_name必填

版本历史

1
  1. v0.1.0最新Oct 31, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分