Strety MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRETY_CLIENT_ID | Yes | Your Strety OAuth client ID | |
| STRETY_ACCESS_TOKEN | Yes | Your Strety access token | |
| STRETY_CLIENT_SECRET | Yes | Your Strety OAuth client secret | |
| STRETY_REFRESH_TOKEN | Yes | Your Strety refresh token |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| strety_list_todosA | List todos from Strety. Can filter by assignee name and completion status. Returns todos sorted by due date. |
| strety_get_todoA | Get full details of a specific todo by its ID |
| strety_list_peopleA | List all people in the Strety organization. Useful for finding assignee names/IDs. |
| strety_list_goalsA | List goals (rocks) from Strety. Can filter by assignee name and completion status. Returns goals sorted by due date. |
| strety_create_todoA | Create a new todo in Strety. Returns the created todo with its ID. |
| strety_update_todoA | Update an existing todo in Strety. Only provide fields you want to change. Handles ETag automatically. |
| strety_complete_todoA | Mark a todo as complete (or uncomplete it). Handles ETag automatically. |
| strety_delete_todoA | Permanently delete a todo from Strety. This cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clear and distinct purpose: separate operations for todos (create, read, update, delete, complete), listing goals, and listing people. No ambiguity between tools.
All tools follow a consistent 'strety_verb_noun' pattern (e.g., strety_create_todo, strety_list_goals). The naming is predictable and uniform.
With 8 tools, the server covers core functionality without being over- or under-scoped. Each tool serves a necessary role in managing todos and referencing goals and people.
The todo operations are complete (CRUD plus completion toggle). However, goals and people are only listable, lacking create/update/delete, which is a minor gap for a full lifecycle.