db4app Todo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_SCHEMA | No | Schema name for todo tables | todo_mcp |
| MCP_AUTH_TOKEN | No | Auth token for authentication (alternative to full URL) | |
| MCP_POSTGRES_URL | No | Postgres connection URL (format: postgres://postgres:AUTH_TOKEN@CONNECTION_ID.pg.db4.app) | |
| MCP_CONNECTION_ID | No | Browser connection ID (alternative to full URL) |
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 |
|---|---|
| add_todoB | Add a new todo item to the list. Use this when the user wants to create a new task or reminder. You can specify title, description, category, priority, and due date. |
| mark_as_doneB | Mark a todo item as completed. Use this when the user wants to complete a task. Provide the todo ID. |
| list_todosB | List todos with optional filters. Use this when the user wants to see their todos. You can filter by completion status, category, or priority. |
| remove_todoB | Remove a todo item from the list. Use this when the user wants to delete a task. Provide the todo ID. |
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 4 tools
Each tool has a clearly distinct purpose with no overlap: add_todo creates items, list_todos retrieves them, mark_as_done updates completion status, and remove_todo deletes items. The descriptions reinforce these distinct roles, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern with snake_case (add_todo, list_todos, mark_as_done, remove_todo). The verbs are descriptive and aligned with CRUD operations, creating a predictable and readable naming convention throughout the set.
With 4 tools, this server is well-scoped for a todo management domain, covering essential CRUD operations without bloat. Each tool earns its place by addressing a core need in the todo lifecycle, making the count appropriate and efficient for the server's purpose.
The tool set provides complete CRUD coverage for todo items (create, read, update, delete) and includes filtering capabilities. A minor gap exists in lacking an explicit update_todo tool for modifying non-completion fields like title or due date, but agents can work around this by removing and re-adding items.