<!-- source: https://vectoralix.com/docs/quickstart | service: Vectoralix | format: markdown twin auto-generated from the canonical HTML page -->

Get Started

#  Quick Start 

 From zero to a served MCP request in about ten minutes. Everything is done in the dashboard — no Git account, no external client, no token work required for this path.

 ## Before you begin

- A modern browser.
- An email address you can receive a verification mail at.
- Five to ten sentences of content you would like an AI client to be able to read — anything will do.
 
## Step 1 — Create an account and organisation

 Sign up from the home page, confirm the verification email, and sign in. Your first organisation is created automatically and every server you create from now on belongs to it.

 You can change the organisation name later from the Organisations area in the dashboard. For Quick Start the default is fine.

## Step 2 — Create your first MCP server

1. Open the MCP Servers list from the sidebar and click "Create MCP Server".
2. Give it a name and a slug. The slug is used in the public endpoint URL.
3. Leave Visibility set to Public — that means clients can connect with no authentication, which is the shortest path to a working request.
4. Save. You land on the server's edit page, which is split across six tabs: Details, Contents, Categories, Groups, Relations, Versions.
 
## Step 3 — Add one piece of content

1. Switch to the Contents tab and click Create.
2. Choose Typed content as the source.
3. Paste your paragraph into the editor, give the record a name, and save.
 
 The content is stored as a database record keyed by a unique slug. There is no S3, no metadata layer — just the body of what you typed.

## Step 4 — Activate version 1

1. Switch to the Versions tab and click Create Version.
2. You can leave the optional release note blank for now.
 
 Version 1 is special: it is auto-set as both the active version (what the endpoint serves) and the default version (the fallback if the active is ever cleared). Subsequent versions require an explicit Activate click.

## Step 5 — Enable File Search

 On the Details tab, toggle File Search on and save. With default settings you do not need to configure anything else — five capabilities (list\_categories, list\_groups, full\_text\_search, list\_files, search\_related) are registered as MCP tools immediately.

## Step 6 — Try it in the Playground

1. Open MCP Playground from the sidebar.
2. Click Quick-connect on your server's row, or paste the endpoint URL manually.
3. In the Tools tab, run list\_files — you should see your typed content listed.
4. Run full\_text\_search with a keyword that appears in your paragraph and confirm the matched record comes back.
 
 The Playground is a thin Livewire client around your MCP endpoint — every request you send shows up in the JSON-RPC request/response log at the bottom of the page so you can see exactly what an AI client would see.

 **What you just built:** A public MCP server with one piece of content, File Search enabled, and an active version that any MCP-aware client can hit immediately. From here, the longer "Your First MCP Server" walkthrough shows how to add multiple content types, custom tools, private auth, and a real client integration.
