Reference
Connect a client
TuskPoint speaks the Model Context Protocol over stdio, so any MCP-capable client can use all eleven tools. Pick your client below, the config is the same shape everywhere; only the file location changes.
One block, every client
{ "mcpServers": { "tuskpoint": { … } } } block (VS Code uses servers, and Codex CLI uses TOML, both shown below). The launcher is always uvx tuskpoint-mcp, so there is no repo to clone and no cwd to set. Or just call the tuskpoint_info tool and let the agent emit the right snippet for you.Claude Desktop
Edit claude_desktop_config.json (Settings → Developer → Edit Config) and add the server, then restart Claude Desktop.
{
"mcpServers": {
"tuskpoint": {
"command": "uvx",
"args": ["tuskpoint-mcp"],
"env": {
"WALRUS_AGGREGATOR_URL": "https://aggregator.walrus-testnet.walrus.space",
"WALRUS_PUBLISHER_URL": "https://publisher.walrus-testnet.walrus.space"
}
}
}
}Claude Code
Register it from the CLI in one line.
claude mcp add tuskpoint -- uvx tuskpoint-mcpThen confirm it is wired up:
claude mcp listCursor
Create .cursor/mcp.json in your project (or the global ~/.cursor/mcp.json) with the same block.
{
"mcpServers": {
"tuskpoint": {
"command": "uvx",
"args": ["tuskpoint-mcp"],
"env": {
"WALRUS_AGGREGATOR_URL": "https://aggregator.walrus-testnet.walrus.space",
"WALRUS_PUBLISHER_URL": "https://publisher.walrus-testnet.walrus.space"
}
}
}
}Windsurf
Add the block to ~/.codeium/windsurf/mcp_config.json and reload the MCP servers from the Cascade panel.
{
"mcpServers": {
"tuskpoint": {
"command": "uvx",
"args": ["tuskpoint-mcp"],
"env": {
"WALRUS_AGGREGATOR_URL": "https://aggregator.walrus-testnet.walrus.space",
"WALRUS_PUBLISHER_URL": "https://publisher.walrus-testnet.walrus.space"
}
}
}
}Gemini CLI
Add the block to ~/.gemini/settings.json (or the project-local .gemini/settings.json). Gemini CLI uses the same mcpServers shape and expands env vars automatically.
{
"mcpServers": {
"tuskpoint": {
"command": "uvx",
"args": ["tuskpoint-mcp"],
"env": {
"WALRUS_AGGREGATOR_URL": "https://aggregator.walrus-testnet.walrus.space",
"WALRUS_PUBLISHER_URL": "https://publisher.walrus-testnet.walrus.space"
}
}
}
}VS Code (GitHub Copilot)
In Copilot agent mode, create .vscode/mcp.json in your workspace. VS Code uses a top-level servers key with an explicit type.
{
"servers": {
"tuskpoint": {
"type": "stdio",
"command": "uvx",
"args": ["tuskpoint-mcp"]
}
}
}OpenAI Codex CLI
Codex CLI is configured in TOML. Add a [mcp_servers.tuskpoint] table to ~/.codex/config.toml.
[mcp_servers.tuskpoint]
command = "uvx"
args = ["tuskpoint-mcp"]Any other MCP client
A ready-to-use .mcp.json ships in the repo root. Point your client at it, or copy the block above. The transport is stdio and the command is always uvx tuskpoint-mcp.
Every config on this page is also served as plain text at one URL, so you or an agent can fetch the whole setup with a single command:
curl -sL https://tuskpoint.xyz/skills/setupEnable semantic search with MemWal
Plain-English recall is a core part of TuskPoint. To power checkpoint_search, add your MemWal credentials to the env block (or your .env):
MEMWAL_PRIVATE_KEY=your_ed25519_delegate_key_hex
MEMWAL_ACCOUNT_ID=your_walrus_memory_account_object_idFree on testnet, funded on mainnet
testnet, where checkpoint_save and checkpoint_fork work out of the box for free. To run on mainnet you need a publisher with a funded key, see the network guide for the switch.