Firestore Todo List MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIREBASE_PROJECT_ID | Yes | Your Firebase project ID | |
| FIRESTORE_COLLECTION | Yes | The Firestore collection name to use for storing todos | |
| FIRESTORE_EMULATOR_HOST | No | Firestore emulator host (for development mode only) | |
| FIREBASE_SERVICE_ACCOUNT | No | Base64 encoded Firebase service account JSON file |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_todosB | List todo items from the user's 'todos' store with optional filters. |
| create_todoB | Add a new todo/task item to the user's store |
| update_todoC | Update fields of an existing todo item (text, completed, dueDate, role). |
| complete_todoB | Mark an existing todo item as completed. |
| delete_todoA | Delete a todo item from the user's Firestore 'todos' collection by id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create-todo-guide | Guides for adding a new task, following todo manager rules. |
| complete-todo-guide | Guide for completing or partially completing tasks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| todo-manager-spec | Field definitions and semantics for todo items. |
| todo-manager-tool-rules | When and how to use list_todos, create_todo, update_todo, complete_todo, delete_todo. |
| todo-manager-flow-rules | Rules for creating, completing, and splitting tasks. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose targeting specific CRUD operations on todo items: create, list, update, delete, and complete. No overlap exists between tools, making it easy for an agent to select the correct one based on the intended action.
All tool names follow a consistent verb_noun pattern with 'todo' as the noun (e.g., create_todo, list_todos). The naming is uniform, using snake_case throughout, which enhances readability and predictability for agents.
With 5 tools, this server is well-scoped for a todo list domain, covering essential operations without bloat. Each tool earns its place by providing core functionality, making the set efficient and manageable for typical use cases.
The toolset offers complete CRUD coverage for todo items, including create, read (list), update, delete, and a specialized complete action. There are no obvious gaps; agents can perform all necessary lifecycle operations without dead ends.