todomate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODOMATE_EMAIL | Yes | Email address for Firebase authentication. | |
| TODOMATE_MCP_HOST | No | Host to bind the HTTP server. | 127.0.0.1 |
| TODOMATE_MCP_PORT | No | Port to bind the HTTP server. | 8000 |
| TODOMATE_PASSWORD | Yes | Password for Firebase authentication. After a successful request, a refresh token is saved to .env and subsequent runs may not require this password. | |
| TODOMATE_MCP_PUBLIC_URL | No | Public HTTPS URL for reverse proxy deployment, e.g. https://todos.example.com/mcp | |
| TODOMATE_FIREBASE_API_KEY | Yes | Firebase API key used for authentication. | |
| TODOMATE_MCP_ACCESS_TOKEN | No | Bearer token required for HTTP server mode. Not needed for stdio mode. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_todosA | List the authenticated user's todos for a date. Defaults to today in Asia/Seoul. |
| get_todoA | Get one of the authenticated user's todos by ID. |
| create_todoB | Create a todo for the authenticated user. Date defaults to today in Asia/Seoul. |
| update_todoC | Update provided fields of one authenticated user's todo. |
| complete_todoC | Mark one authenticated user's todo complete or incomplete. |
| delete_todoA | Delete one authenticated user's todo by 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 | |
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/LYJ0304/todomate-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server