Kriyan MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Kriyan MCP ServerList my incomplete tasks in the Work space, most recent first."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kriyan
Kriyan is an open-source planner for tasks and goals across School, Business and Life. The web app uses Clerk for identity, Convex for isolated realtime data, and a Clerk OAuth-protected MCP endpoint for AI clients. Task length is optional.
Repository layout
apps/web/ Next.js 16 web app, public assets and MCP routes
packages/backend/ Convex schema, functions and shared operations
packages/core/ Pure TypeScript quick-add parser and calendar date helpers
docs/ Implementation plan and approved design prototypeThe repository uses Bun workspaces with hoisted dependencies. React and React DOM are pinned to 19.2.3. The backend package exports its generated API and data model through @kriyan/backend/convex/_generated/api and @kriyan/backend/convex/_generated/dataModel.
Related MCP server: Todoist AI MCP Server
Local development
Use Bun 1.3.14. Run these commands from the repository root:
Install dependencies with
bun install.Copy
apps/web/.env.exampletoapps/web/.env.localand fill in your Clerk and Convex configuration. Environment files remain ignored by Git.Start the backend:
cd packages/backend && bunx convex dev. The first run links the folder to your Convex project and writesCONVEX_DEPLOYMENTtopackages/backend/.env.local.In another terminal, start the web app with
bun run dev.
Open http://localhost:3000. Next.js loads the web app's environment from apps/web/.env.local.
Required configuration
The web app needs NEXT_PUBLIC_CONVEX_URL, NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, the Clerk server key, and SERVICE_SECRET. Clerk needs a JWT template named convex with aud set to convex. The Convex deployment needs CLERK_JWT_ISSUER_DOMAIN and the same random SERVICE_SECRET used by the web server. Keep the service secret in server environments, without a NEXT_PUBLIC_ prefix. Set SERVICE_SECRET in both Convex and the web environment. MCP_SERVICE_SECRET is accepted as a temporary fallback; existing local env files are not changed. The signed envelope is [timestamp, nonce, ownerId, operation, payload], with a five-minute window and replay protection.
To configure your Convex deployment, run the following from packages/backend with your own values:
bunx convex env set CLERK_JWT_ISSUER_DOMAIN https://your-clerk-issuer.example
bunx convex env set SERVICE_SECRET your-random-secretMCP
Connect an OAuth-capable MCP client to https://kriyan.vercel.app/mcp.
kriyan.app is the public landing page. Product and automation routes redirect to the app host at kriyan.vercel.app.
The server advertises OAuth metadata under /.well-known/, authenticates through Clerk, and exposes these user-scoped tools:
list_tasks,get_task,create_task,update_task,complete_tasklist_spaces,create_spacesearch_notes
Commands and verification
Run from the repository root:
bun install
bun run dev
bun run typecheck
bun run lint
bun run test
bun run builddev and build run the web workspace. typecheck generates Next.js route types and checks all workspaces. lint and test run each workspace that defines the corresponding script. The web app defines linting; core defines Bun tests for the parser and date helpers, and backend defines Vitest tests using convex-test. To serve a production build, run bun run --filter @kriyan/web start.
GitHub Actions runs installation with --frozen-lockfile, typechecking, linting, tests and the web build for pull requests and pushes to main or v2. The CI build uses fake Convex, Clerk publishable-key and MCP secret placeholders. They permit build-time validation without production credentials; use your own configuration to run the app.
License
MIT
This server cannot be deployed
Related MCP Connectors
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Manage tasks, Focus Zone, notes, projects, and task history from compatible AI assistants.
AI-native task management: list, create, update and archive tasks with rich context for AI agents
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage Google Tasks through natural language interactions. Supports creating, updating, deleting, searching, and listing tasks with secure OAuth2 authentication.130 npm10MIT

Todoist AI MCP Serverofficial
AlicenseAqualityAmaintenanceEnables AI agents to access and modify Todoist accounts to manage tasks and projects on the user's behalf. It provides a suite of tools for task operations and supports interactive UI widgets for a rich visual experience in AI chat interfaces.473,762 npm553MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Google Tasks, including listing, creating, updating, deleting, and completing tasks via the Google Tasks API.84 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to securely authenticate with Google Tasks and perform full CRUD operations on task lists and tasks, including moving tasks and clearing completed tasks.37 npm-