Skip to main content
Glama
Firestore Todo List MCP Server

Firestore Todo List MCP Server

by gtoshinakano

Firestore Todo List MCP Server

Connect any MCP Client like Claude, Open-WebUI and others to this MCP server to manage todos via AI chat in an opinionated way.

You can simply tell the model to create_todo, list_todos, update_todo, 'complete_todo' and delete_todo

You can setup a custom system prompt as well to get customized answers.

Works very well with Claude, OpenAI and Deepseek models (paid versions). Local models in Ollama also works, but with limitations.

Data is stored on Firebase Firestore because it is "free" for personal usage, easy to run, and easy to setup.

This is an experimental project I created just for learning purposes.

Feel free to try.

Getting Started

Use the Firestore Todo MCP Server on Claude (and others)

Edit the claude_desktop_config.json or the mcp configuration file of your LLM client

{
    "mcpServers": {
        "firestoreTodoMcp": {
            "command": "npx",
            "args": [
                "firestore-todo-mcp"
            ],
            "env": {
                "FIREBASE_SERVICE_ACCOUNT": "base64(serviceAccount.json)",
                "FIREBASE_PROJECT_ID": "your-firebase-project-id",
                "FIRESTORE_COLLECTION": "test_collection"
            },
            "type": "stdio"
        }
    }
}

Don't forget to setup your project on Firebase and to get the Firebase serviceAccount from the project's configuration.

The file content must be 'base64' encoded when passing the value to the json above.

Related MCP server: Todoist MCP Server

Development Mode

1. Clone the repo

git clone https://github.com/gtoshinakano/firebase-todo-mcp.git
cd firebase-todo-mcp

2.Run Firestore emulator

Install firebase-tools cli, do firebase login, install emulators and run

firebase emulators:start --only firestore --project local-todo-dev

3.Testing on Inspector

Check if all tools are working fine, test input parameters, output params

npx @modelcontextprotocol/inspector \
    -e FIRESTORE_EMULATOR_HOST=localhost:3333 \
    -e FIREBASE_PROJECT_ID=local-todo-dev \
    -e FIRESTORE_COLLECTION=test_collection \
    tsx bin/index.ts

4. (Optional) Build and Configure Claude mcp configuration locally

{
    "mcpServers": {
    "firestore-todo": {
        "command": "node",
        "args": ["/absolute/path/to/dist/bin/index.js"],
        "env": {
        "FIRESTORE_EMULATOR_HOST": "localhost:3333",
        "FIREBASE_PROJECT_ID": "local-todo-dev",
        "FIRESTORE_COLLECTION": "test_collection"
        }
    }
    }
}

5. Create a project with a system prompt from the example

Copy the contents of the system prompts from the path example/ complete: More effective, but token expensive short: Shorter version for saving tokens. Works fine but less accurate

6. Have fun with your new Task Manager ;)

Try chat like: Add the task XYZ. Due date tomorrow.

You can be more specific and tell the situation: I forgot to talk to John regarding XYZ on Friday and I need this ASAP

Or you can be broad and Claude will try to help you split the big task into smaller ones (doesn't work well with Ollama models :/): I need to create my XYZ Vague Project

Available Tools

5 tools
complete_todoComplete todo/taskB

Mark an existing todo item as completed.

Inputs: id (required), archive, completionNotes. Returns: todo

create_todoCreate todo/taskB

Add a new todo/task item to the user's store

Inputs: title (required), role (required), details, completed, +2 more. Returns: todo

delete_todoDelete todo/taskA

Delete a todo item from the user's Firestore 'todos' collection by id.

Inputs: id (required). Returns: deletedId

list_todosList todos/tasksB

List todo items from the user's 'todos' store with optional filters.

Inputs: completed, archived, from, to, +2 more. Returns: todos

update_todoUpdate todo/taskC

Update fields of an existing todo item (text, completed, dueDate, role).

Inputs: id (required), title, details, completed, +5 more. Returns: todo

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers