Sunsama MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port for HTTP transport | 3000 |
| SESSION_TTL | No | Session timeout in milliseconds | 3600000 |
| MAX_SESSIONS | No | Maximum concurrent sessions | 100 |
| TRANSPORT_MODE | No | Transport type: stdio or http | http |
| CLIENT_IDLE_TIMEOUT | No | Client idle timeout in milliseconds | 900000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-userB | Get current user information including profile, timezone, and group details |
| get-tasks-backlogC | Get tasks from the backlog |
| get-tasks-by-dayB | Get tasks for a specific day with optional filtering by completion status |
| get-archived-tasksC | Get archived tasks with optional pagination |
| get-task-by-idC | Get a specific task by its ID |
| create-taskC | Create a new task with optional properties |
| delete-taskC | Delete a task permanently |
| update-task-completeC | Mark a task as complete with optional completion timestamp |
| update-task-snooze-dateB | Update task snooze date to reschedule tasks or move them to backlog |
| update-task-backlogC | Move a task to the backlog |
| update-task-planned-timeC | Update the planned time (time estimate) for a task |
| update-task-notesB | Update the notes content for a task |
| update-task-due-dateC | Update the due date for a task |
| update-task-textC | Update the text/title of a task |
| update-task-streamC | Update the stream/channel assignment for a task |
| get-streamsB | Get streams for the user's group (streams are called 'channels' in the Sunsama UI) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Sunsama API Documentation | Documentation for the Sunsama API endpoints and data structures |
TDQS
Scored across 16 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity. For example, 'get-task-by-id' retrieves a single task, while 'get-tasks-by-day' fetches tasks for a date, and various 'update-task-*' tools each modify a specific property like due date or notes without overlap.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. All tools start with verbs like 'create', 'delete', 'get', or 'update', followed by a clear noun or modifier, making them predictable and readable.
With 16 tools, this server is well-scoped for task management in Sunsama, covering essential operations like CRUD for tasks, user info, streams, and specific updates. Each tool earns its place by addressing distinct aspects of the domain without being excessive.
The tool surface provides complete CRUD/lifecycle coverage for tasks, including creation, retrieval by various criteria, updates for all key properties, deletion, and archival. It also covers related resources like streams and user info, with no obvious gaps for the task management domain.