Vectros AI MCP

@vectros-ai/mcp-server

One-click badges install the server entry in your client. You still supply

a key — run npx -y @vectros-ai/cli bootstrap (recommended) or paste your

ssk_.... See Connect from your client and the

honest caveats.

A Model Context Protocol server for Vectros — a typed, multi-tenant record store unified with hybrid search and citation-grounded RAG. Deterministic lookups and enumeration *and* semantic search over one isolated, per-customer index of records and documents — so an agent gets memory that's precise, not just fuzzy recall. Reached agent-natively here over MCP (Claude Desktop, Cursor, Claude Code, Cline, Continue, VS Code, hosted platforms) — and the same data is human-accessible through the Vectros app + SDKs.

npx -y @vectros-ai/mcp-server

Your agent can search your indexed corpus, query structured records, ingest documents, and ask questions grounded against documents — reaching only your tenant's data, never the public web (there are no web tools).

Quick start — one command

The fastest way to set up is the @vectros-ai/cli bootstrap command. It mints a least-privilege scoped key (ssk_*) bound to a narrowed AccessProfile, optionally scaffolds a use-case data model, and safe-merges the vectros server into your MCP client config — no root key, and no hand-editing JSON:

npx -y @vectros-ai/cli bootstrap

You pick what to set up (a blank read-only credential, or a blueprint like task tracking) and sign in once with a token from the developer portal. The command then:

• mints a scoped ssk_* for this machine (independently rotatable),
• creates the matching AccessProfile — data-plane only; the command refuses to provision control-plane scope (keys / profiles / billing / …),
• backs up and merges the entry into claude_desktop_config.json (Claude Desktop, Cursor, Cline). For Claude Code, add --client code: it merges the project .mcp.json and prints the equivalent claude mcp add command.

Restart your MCP client and you're done. It's idempotent (re-run any time); --rotate replaces this machine's key.

Want to browse the data yourself? bootstrap sets up the key for your *agent*, not a login for *you* — so a blueprint's context won't appear in the data-plane app's switcher until you join your own user to it (the app lists only contexts your user has access in). Grant yourself a role once, either in the admin app (Access → Contexts → _your context_ → Profiles → Create profile, pick yourself from the by-email picker, choose a role — no raw id needed) or from the CLI with --principal me (resolves to your own user):

vectros access grant --principal me --context <context-id> --role <role>

Blueprints that ship a human role (e.g. agentic-sdlc's editor) let you use --role; otherwise grant inline scopes with --actions records:r,search:r,….

For scripted / agent use, set the sign-in token in the environment and skip the prompts:

VECTROS_BOOTSTRAP_TOKEN=… npx -y @vectros-ai/cli bootstrap \

--blueprint task-management --yes

Prefer to wire it up by hand? See Configure manually below.

Connect from your client

The fastest path on every client is npx -y @vectros-ai/cli bootstrap — it mints a scoped key and writes the config for you. The one-click buttons install the server entry; you then supply the key (bootstrap, or paste your ssk_...).

Codex (~/.codex/config.toml):

[mcp_servers.vectros]

command = "npx" args = ["-y", "@vectros-ai/mcp-server"] env = { VECTROS_API_KEY = "ssk_live_..." }

Honest caveats

Precision is the pitch — what this server deliberately does *not* do:

• There's a human step. Bootstrap needs a developer-portal sign-in / bridge token. One command, but a person signs in — there is no fully unattended provisioning.
• No web tools, on purpose. The agent surface has no web-search or web-fetch tools at all. Vectros is the memory, not the browser.
• Agent document upload is text-inline today. An agent ingests document text inline; on the stdio transport a jailed local-file upload is supported, but bulk file upload from the agent surface isn't the path today.
• **Audit history is tamper-*evident*, not tamper-proof.** A state-continuity chain makes out-of-band alteration *detectable*; it is not continuous automated verification.

Configure manually (Claude Desktop or any MCP client)

If @vectros-ai/cli is installed globally (npm install -g @vectros-ai/cli, not a one-off npx run — the server needs vectros to still be on PATH later, when IT runs, not just while bootstrap ran) and you've run vectros bootstrap with it, omit the env block entirely — the server resolves your key from the local vectros CLI keyring automatically (see Credential resolution below). vectros login alone does not do this — it stores a separate sign-in session, not this key — so bootstrap is the step that actually has to have run:

{

"mcpServers": { "vectros": { "command": "npx", "args": ["-y", "@vectros-ai/mcp-server"] } } }

No CLI installed, or a machine you can't log in on? Set the key directly instead:

{

"mcpServers": { "vectros": { "command": "npx", "args": ["-y", "@vectros-ai/mcp-server"], "env": { "VECTROS_API_KEY": "ssk_live_..." } } } }

This file lives under Claude Desktop's own per-user app-support directory, not a shared repo — but a real key pasted into it is still a live secret at rest: don't paste it into a chat, ticket, or screenshot with the value intact, and prefer the keyring form above whenever you can.

Restart Claude Desktop. The agent now sees the Vectros tools and two resources as callable surfaces.

Configure manually (Claude Code)

Claude Code reads a project-scoped .mcp.json with the same shape. Never commit a real key into it — .mcp.json is exactly the kind of file teams check in to share a project's tooling, and a live ssk_*/sk_* value inside it is a credential leak the moment it lands in git history, not just if the repo is public.

The way to share this config safely: commit the entry with no `env` block at all, and let each developer's own vectros CLI keyring supply the key (see Credential resolution below — this is the same delegation git credential / docker-credential-* use). This needs each teammate to have @vectros-ai/cli installed globally and to have run vectros bootstrap with it — npx-ing the CLI once, or running vectros login alone (a separate sign-in session, not this key), leaves nothing on PATH or in the keyring for the server to find later:

{

"mcpServers": { "vectros": { "command": "npx", "args": ["-y", "@vectros-ai/mcp-server"] } } }

Or let Claude Code's CLI write that keyring-based entry for you:

claude mcp add vectros -- npx -y @vectros-ai/mcp-server

If a machine genuinely has no vectros CLI installed, you can pass the key directly with -e VECTROS_API_KEY=ssk_live_... — but then keep that config local: add .mcp.json to .gitignore first, rather than committing it with the key inside.

Add -e VECTROS_API_BASE_URL= to point the server at a different environment.

Load it into a session by restarting. A Claude Code session that was already open when you added the server won't pick it up mid-session — fully quit and reopen the project (not just re-select the tab). The /mcp panel shows the connector marketplace, not locally-configured stdio servers, so it won't confirm the server is loaded — ask the agent to call a Vectros tool instead. Config is keyed by the git common root, so a linked worktree resolves to its main repo's .mcp.json — add and open from the same project.

Windows note: if your .npmrc (or a global npm config) points the

@vectros-ai scope at another registry, a bare npx -y @vectros-ai/mcp-server

can resolve a build other than the public release. If the command above fails

to start, either remove the scoped-registry override for a plain npx run, or

pin an explicit version (npx -y @vectros-ai/mcp-server@ ) known to

work.

Tools (23 tools)

Search & RAG

Records (structured, schema-validated data)

| Tool | What it d