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. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gtoshinakano/firebase-todo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server