Space MCP server

Space

Space is a workspace your AI agents share with you: documents, tasks, databases and long-term memory that agents read and write over MCP, with a website where you see, correct and edit the same work. Connect Claude Code, Codex, Cursor or any MCP client, and what one session learns is there for the next one.

This repository is the open-source, self-hosted edition. It runs on one machine you control, such as a small VPS, with Docker Compose. It needs no cloud account: no hosted database, object storage, key service or sign-in provider.

What you get

• Documents and tasks with full revision history, edited from the website or by agents.
• Databases: typed tables and boards, which agents can query and change with SQL.
• Agent memory: handoffs between sessions, and claims agents remember, recall with citations, correct and forget.
• Search and recall across everything in the Space, by words; by meaning too once a model provider is configured.
• One MCP endpoint for every agent, with a revocable token or browser sign-in per agent and attribution of who wrote what.
• A REST API with personal API keys, and signed webhooks when database rows change.
• Projects, folders, sections and categories that agents follow when they file new work.

How it is built

Content is stored as readable JSON in PostgreSQL. There is no application-level encryption: whoever operates the server can read the data, as with any self-hosted application. Back up the database and protect the server accordingly.

Install

You need a Linux server with at least 1 GB of memory, such as a small VPS, and, for public access, a domain name whose DNS record points at it. On the server, run:

curl -fsSL https://raw.githubusercontent.com/Hugo-SEQUIER/getspace/main/scripts/install.sh | sudo bash

The installer installs Docker if it is missing, downloads the latest release into /opt/space, asks for the access mode, your domain and your name, starts Space and prints its address and access key. To do the same steps by hand:

git clone https://github.com/Hugo-SEQUIER/getspace.git
cd getspace
git checkout "$(git tag -l 'v*' | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -n 1)"   # latest release
scripts/setup.sh                 # asks for the access mode and your domain, writes .env
docker compose up -d             # downloads the released images and starts everything
docker compose exec api python -m space.check   # checks every setting, in plain words

Both offer two access modes:

• Key mode (default): Space is reachable from the internet at https://your-domain. The website asks for the instance's access key once per browser, and each agent connects with its own revocable token. Point a DNS record at the server and open ports 80 and 443; Caddy obtains the certificate.
• Private mode: no access check at all. Space listens on 127.0.0.1:8080 and you reach it through an SSH tunnel or a VPN such as Tailscale. Never expose this mode publicly.

There are no user accounts: one installation belongs to one person, the owner. Self-hosting covers both modes, every setting, upgrades, backups and troubleshooting.

Moving from the hosted Space? Export your Space there and import it here: Moving from the hosted Space.

Connect an agent

Open Agents → Connect an agent on the website, choose a name and whether the agent may write, and copy the setup it shows. For Claude Code:

Shortened. The full README is on GitHub.