Docs

MCP

The public API and MCP are on every plan — Free included. Bring the tools you already trust; we don't ship a chatbot, and we never train on your work.

Streamable HTTP at https://sahnga.com/mcp. Same personal access token as the REST API. The MCP handler validates the token and calls the internal services directly — it never forwards that token to /api/v1.

Mint a token in account settings— pick the workspace and what the token may view or edit. The workspace is bound in token metadata, never encoded in the secret. Then drop this into Cursor's mcp.json:

{
  "mcpServers": {
    "sahnga": {
      "url": "https://sahnga.com/mcp",
      "headers": {
        "Authorization": "Bearer sng_YOUR_TOKEN"
      }
    }
  }
}

Tools

  • whoami

    Token name, grants, bound workspace ids. No workspaceId.

  • list_projects

    Projects the token owner can see.

  • list_tasks

    Tasks in a project.

  • get_task

    One task by id.

  • search_tasks

    Title prefix search.

  • create_task

    Create a task. Requires tasks.create.

  • update_task

    Update a task. Requires tasks.update.

  • list_comments

    Comments on a task. Requires comments.view.

  • add_comment

    Comment on a task. Requires comments.create.

  • my_tasks

    Tasks assigned to you.

Sahnga still ships no chatbot and never trains on workspace data. Writes show as the token name. Omit workspaceId when the token is bound to one workspace. Call whoami if you are unsure.