Streamline MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPABASE_URL | Yes | The Supabase project URL (e.g., https://YOUR_PROJECT_ID.supabase.co) | |
| SUPABASE_API_KEY | Yes | The Supabase service_role API key | |
| SUPABASE_USER_ID | Yes | The Supabase User UUID |
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 |
|---|---|
| search_tasksB | Search tasks by name, tags, due date, or status. |
| read_taskC | Get full details of a task by UUID. |
| create_taskC | Create a new task. |
| update_taskC | Update a task. |
| complete_taskC | Mark a task as completed or uncompleted. |
| delete_taskC | Move task to trash or delete permanently. |
| search_notesC | Search notes by title, content, or tags. |
| read_noteC | Get full content of a note by UUID. |
| create_noteC | Create a new note with markdown content. |
| update_noteB | Update a note. Use 'append' to add to existing content. |
| delete_noteC | Move note to trash or delete permanently. |
| list_tagsB | List all tags with usage counts. |
| create_tagC | Create a new tag. |
| tag_itemC | Add a tag to a task or note. |
| untag_itemC | Remove a tag from a task or note. |
| list_workspacesB | List all workspaces. |
| read_workspaceC | Get workspace details. |
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 17 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource type (task, note, tag, workspace) and action (create, read, update, delete, list, search, tag/untag), making it easy for an agent to select the correct one. For example, 'create_note' vs 'update_note' and 'tag_item' vs 'untag_item' are well-differentiated.
Tool names follow a consistent verb_noun pattern throughout, such as 'create_task', 'read_note', 'update_note', 'delete_task', 'list_tags', 'search_notes', 'tag_item', and 'untag_item'. All names use snake_case and clear verbs, making the set predictable and readable.
With 17 tools, the count is well-scoped for a task and note management system. Each tool earns its place by covering essential CRUD operations, listing, searching, and tagging functionalities across multiple resource types, without being excessive or too sparse.
The tool surface provides complete CRUD/lifecycle coverage for tasks, notes, tags, and workspaces. It includes create, read, update, delete, list, and search operations, plus tagging/untagging capabilities, with no obvious gaps. Agents can perform all core workflows without dead ends.