sndo

sndo is a Model Context Protocol (MCP) server that securely exposes a user’s personal context (areas, tasks, notes, achievements) via API key–based access, designed for AI agents and MCP-compatible clients.

Requirements

• Node.js 18+ or Bun (recommended)
• An API key generated from 👉 https://sndo.vercel.app

Installation

npm install -g @snvshal/sndo
# or
bun add -g @snvshal/sndo

MCP Client Configuration

sndo communicates over stdio, as required by MCP-compatible clients.

Option 1: Global installation (recommended)

If installed globally, use the sndo binary directly:

{
  "mcpServers": {
    "sndo": {
      "name": "sndo",
      "command": "sndo",
      "args": [],
      "env": {
        "SNDO_API_KEY": "your_sndo_api_key_here"
      }
    }
  }
}

Option 2: No global installation (via npx / bunx)

If you don’t want a global install, run via npx (Node) or bunx (Bun):

{
  "mcpServers": {
    "sndo": {
      "name": "sndo",
      "command": "npx",
      "args": ["-y", "@snvshal/sndo"],
      "env": {
        "SNDO_API_KEY": "your_sndo_api_key_here"
      }
    }
  }
}

Recommendation: Use Option 1 when possible. Use Option 2 for quick setup or sandbox environments.

Authentication

sndo uses Bearer API keys.

Provide your API key via environment variable:

export SNDO_API_KEY=your_api_key_here

or directly inside your MCP client configuration.

MCP Tools

Context

• get_context

  • Returns:

    • Areas
    • Tasks
    • Notes
    • Last updated timestamps

Achievements

• get_achievements

  • Fetch achievements
  • Defaults to today
  • Supports date filtering

• add_achievement

  • Add a new achievement
  • Optional note support (appends, not overwrites)

API Scopes

API keys use fine-grained scopes for access control.

Supported Scopes

• mcp:areas:read
• mcp:achievements:read
• mcp:achievements:write

Scopes are validated on every request. Missing scopes result in 403 Forbidden.

You can manage scopes per API key from the dashboard: 👉 https://sndo.vercel.app/api-keys

Security Notes

• API keys are hashed at rest
• API usage is tracked per key and per endpoint
• Keys can be revoked instantly
• Never commit API keys to source control

License

MIT