Getting started
Quick start
TuskPoint is a drop-in MCP plugin. One line wires it into your agent, and all eleven tools show up.
1. Add the plugin
uvx fetches and launches TuskPoint on demand, so there is nothing to install or keep running. In Claude Code it is a single command:
claude mcp add tuskpoint -- uvx tuskpoint-mcpThe package is published on PyPI, so uvx resolves it from a clean machine with nothing cloned.
For any other client, drop the same launcher into its MCP config (only the file location changes):
{
"mcpServers": {
"tuskpoint": {
"command": "uvx",
"args": ["tuskpoint-mcp"]
}
}
}See Connect a client for Claude Desktop, Cursor, Windsurf, VS Code, and Codex CLI, or call the tuskpoint_info tool and let the agent emit the right snippet.
Prefer the terminal? Every config block above is also served as plain text at a single URL, so you (or an agent) can fetch the whole setup with one command:
curl -sL https://tuskpoint.xyz/skills/setup2. Keys, only when you need them
What needs keys, and what doesn't
checkpoint_save, checkpoint_fork) need a publisher, and plain-English recall (checkpoint_search) runs on MemWal, so add those credentials to the env block to unlock them. Until you do, the server still starts and those tools return a clear message instead of failing.3. See it live
Watch a real crash-and-resume, a diff, a rollback, and plain-English search on the live run dashboard, where every panel is a live Walrus round-trip.
Run from source (contributors)
Want to hack on the engine itself? Clone and install with all extras. From a checkout the server also runs with python mcp_server/server.py (a thin shim around the packaged tuskpoint-mcp command).
git clone https://github.com/faithabiodun/tuskpoint.git
cd tuskpoint
python -m pip install -e ".[all]"
cp .env.example .env # then fill in your keysNext steps
Browse the full tool reference, learn how fork & replay works, or wire TuskPoint into Claude, Cursor, or Windsurf.