Schema | Todo MCP Server

Todo MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`NODE_ENV`	No	Node.js environment (development or production)	development
`JWT_SECRET`	Yes	Secret key for JWT token signing
`DATABASE_URL`	Yes	PostgreSQL connection string for Neon database
`KINDE_CLIENT_ID`	Yes	Kinde client ID for OAuth authentication
`KINDE_ISSUER_URL`	Yes	Kinde authentication issuer URL (e.g., https://your-domain.kinde.com)
`KINDE_CLIENT_SECRET`	Yes	Kinde client secret for OAuth authentication

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
loginB	Login with Kinde to get authentication token
save_tokenC	Save your Kinde authentication token for future use
list_todosC	List all todos for the authenticated user
get_subscription_statusC	Get the user's subscription status and todo usage
upgrade_subscriptionC	Upgrade user subscription to paid plan
create_todoC	Create a new todo item with interactive prompts
update_todoC	Update an existing todo item with interactive prompts
delete_todoC	Delete a todo item with interactive prompts
logoutA	Logout and clear stored authentication token
get_kinde_billingC	Get Kinde billing information and subscription status
refresh_billing_statusB	Force refresh billing status from Kinde (useful after plan changes)
logoutA	Logout and clear stored authentication token

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sholajegede/todo_mcp_server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server