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, then drop this into Cursor's mcp.json:
{
"mcpServers": {
"sahnga": {
"url": "https://sahnga.com/mcp",
"headers": {
"Authorization": "Bearer sng_YOUR_TOKEN"
}
}
}
}Tools
list_projectsProjects the token owner can see.
list_tasksTasks in a project.
get_taskOne task by id.
search_tasksTitle prefix search.
create_taskCreate a task. Write scope.
update_taskUpdate a task. Write scope.
add_commentComment on a task. Write scope.
my_tasksTasks assigned to you.
Sahnga still ships no chatbot and never trains on workspace data. The token is yours. Every write is attributed to you.