Getting started with SenseLab only takes a few seconds
Get Your Credentials
- Create a SenseLab account
- Go to Settings → API Keys to create a scoped key
- Go to the SenseLab Dashboard → Agents page
- The MCP Connection Card shows your Server URL and a one-line install command with your key already in it
- Run that command, or copy the ready-made JSON snippet into your IDE config
Need more keys? Go to Settings → API Keys to create scoped keys per agent or service.
Connect Your IDE
The fast way: one command
This configures every MCP client on your machine at once, so most people never
need to edit a config file:
It detects the clients you already have — Cursor, Claude Desktop, Claude Code,
Codex, Windsurf, and VS Code — installs uv if it is
missing, writes the config for each one, and pre-warms the server package so your
first session is not a cold start. On Claude Code it also installs a memory skill
that teaches the agent when to reach for memory.
Re-running it is safe — it replaces its own entry and leaves the rest of your
config alone. --uninstall removes it again. See the
MCP Setup guide for every flag and the full tool list.
Manual setup
If you would rather not run a script.
Cursor
Add to .cursor/mcp.json:
Claude Code
Keep the --refresh flag. Without it uvx reuses the build it cached the
first time it ran the server, so you stay on that version even after we ship a
fix.
amfs-mcp-server-pro is the right package whenever you have an API key. The
plain amfs-mcp-server also talks to the API, but it only exposes the
SenseLab Open Source tool surface — no rooms, no negotiations, no documents.
Restart your IDE, then ask the agent to run amfs_stats(). If it returns a
response, you’re connected.
Connect via SDK
Both SDKs talk to local storage unless you hand them an HTTP adapter. Pass one
explicitly — setting the environment variables alone will not connect you to the
hosted service.
Python
TypeScript
Without the adapter, AgentMemory writes to local storage — the filesystem in
Python, memory in TypeScript. Everything appears to work, but nothing reaches
your account and the dashboard stays empty.
Connect via REST API
See the API Reference for the full endpoint list.
Security
Account isolation — SenseLab Security enforces hard isolation at the storage layer, so one account cannot see another’s data even if there’s a bug in application code.
Scoped keys — Restrict keys to specific entity paths and permissions:
Audit logging — Every state-changing operation is recorded. View in Dashboard → Audit Log.
Never hardcode API keys in files committed to git. Use environment variables or a secrets manager.
Troubleshooting