Get Started

Core Concepts

A reference for every noun and invariant the rest of the docs assume. One definition per concept, the invariant that matters, and a pointer to where it is fully explained as those pages come online.

MCP server

A user-created instance with a unique endpoint of the form https://vectoralix.com/mcp/<serverUid>. Each server owns its content, an attached set of tools, and a history of immutable versions. One server, one endpoint, one billable unit of MCP traffic.

Content

Typed documents, file uploads, or Git-imported files stored as database records keyed by a unique slug. Vectoralix only stores the body — there is no metadata layer and no S3.

Categories

User-defined labels you assign to content records. Categories are scoped to a single server.

File groups

Logical bundles of content records used by File Search to give AI clients narrow, contextual slices of your knowledge base instead of a flat list.

Relations

Immutable links between two content records — source, target, and a relation type (e.g. "depends-on"). To change a relation, delete it and create a new one.

Tools

Server-attached capabilities. Three types ship in the box:

  • File Search — five capabilities (list_categories, list_groups, full_text_search, list_files, search_related), each registered as a separate MCP tool.
  • Code Execute — user-authored JavaScript run in a QuickJS sandbox with configurable timeout and memory limits.
  • API URL — proxied HTTP calls to upstream APIs with SSRF protection, OAuth credentials, and optional QuickJS post-processing.

Tools are live, not versioned: configuration changes take effect immediately on every server they are attached to. They are also shareable — one tool can be wired to multiple servers via a many-to-many pivot.

Visibility

Public servers accept unauthenticated traffic. Private servers reject everything that does not carry a valid bearer token. Plan tier can cap the number of private servers per organisation.

Versions

Immutable snapshots of content, groups, and relations at the moment they are cut. Two roles matter:

  • Active — the version currently served by the endpoint. Exactly one at a time.
  • Default — the fallback version. If the active version is deleted, the endpoint falls back to default.

Version 1 is auto-active and auto-default. After that, activation and default assignments are explicit. Switching the active version is immediate — no rebuild, no redeploy.

Request limits

Each server has a per-month request quota tied to your subscription plan. Quotas are enforced per-server, not per-organisation-total. When the quota is exhausted, the endpoint returns a JSON-RPC rate-limit error until the next monthly reset.

Organisation

The billing and ownership boundary. Every server, content record, tool, version, and OAuth credential belongs to exactly one organisation. Plans, quotas, and member access are all attached at the organisation level.

Endpoint URL shape

The canonical request path is fixed: 

POST https://vectoralix.com/mcp/<serverUid>

On every request the runtime resolves the active version (or falls back to default), eager-loads its content and tool configuration, and registers each enabled tool with the MCP runtime before handing the connection to the client.

How the pieces fit together

Organisation
  └── MCP Server
        ├── Content ─── Categories
        │     └── Groups (pivot)
        │     └── Relations (source / target)
        ├── Tools (pivot — shareable across servers)
        └── Versions (snapshot of content, groups, relations)
                 └── Active version + Default version