create_taskLABSCO SUMMARY
Four item types, one search, and files on disk you can still read yourself.
The database is the index and the markdown files in .plan are the human-readable copy, kept in step by the sync tool — so the plan survives being looked at without the server running. Rules being first-class is the unusual part: project conventions live next to the work rather than in a prompt.
What it is
A planning server backed by SQLite with full-text search. It keeps four kinds of item — tasks, features, bugs and rules — and mirrors them to markdown files in a .plan directory inside your project.
What you get
- create_task, update_task, get_task, list_tasks and delete_task, with status, priority and progress
- create_feature, update_feature, get_feature, list_features and delete_feature for user stories and epics
- create_bug, update_bug, get_bug, list_bugs and delete_bug, with severity and reproduction steps
- create_rule, update_rule, get_rule, list_rules and delete_rule for project rules and validations
- search and advanced_search across every plan item, with relevance scoring
- backup_database, restore_database and sync_filesystem
- Resources at plan://index, plan://tasks, plan://features and plan://bugs
Requirements
Node, built from the repository, started against the path of the project you want it to plan. It creates a .plan directory there holding the SQLite database and the mirrored markdown files. No credentials.
Setup effort
Build from source — git clone https://github.com/vibeclasses/follow-plan-mcp.git
USE CASES
01
Filing what you just found without breaking flow
Create the bug with its severity and reproduction steps, or the task with its priority, in the same conversation.
02
Finding everything about one area
Search across tasks, features, bugs and rules at once, ranked by relevance, rather than checking four lists.
03
Keeping the agent to the project's conventions
Store them as rules and read them back at the start of a piece of work.
04
Making the plan readable outside the tool
Sync the database to the markdown files, and take a backup before a large change.
25 tools
Listed in project docs. Your client may show a different list.
update_taskget_tasklist_tasksdelete_taskcreate_featureupdate_featureget_featurelist_featuresdelete_featurecreate_bugupdate_bugget_buglist_bugsdelete_bugcreate_ruleupdate_ruleget_rulelist_rulesdelete_rulesearchadvanced_searchbackup_databaserestore_databasesync_filesystemBEFORE YOU INSTALL
What to know first
Tools you get
25 tools named in the project's documentation.
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/vibeclasses/follow-plan-mcp.git
cd follow-plan-mcp
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"follow-plan": {
"command": "node",
"args": [
"<YOUR_PATH_TO_FOLLOW_PLAN_MCP>/dist/index.js",
"<YOUR_PATH_TO_PROJECT>"
],
"env": {}
}
}
}<YOUR_PATH_TO_FOLLOW_PLAN_MCP> is the full path of the folder git clone created, and <YOUR_PATH_TO_PROJECT> is the project whose .plan folder the server should manage.
VS Code
VS CODE · JSON
{
"servers": {
"follow-plan": {
"command": "node",
"args": [
"<YOUR_PATH_TO_FOLLOW_PLAN_MCP>/dist/index.js",
"<YOUR_PATH_TO_PROJECT>"
],
"env": {}
}
}
}<YOUR_PATH_TO_FOLLOW_PLAN_MCP> is the full path of the folder git clone created, and <YOUR_PATH_TO_PROJECT> is the project whose .plan folder the server should manage.
