@toolsdk.ai/registry 1.0.151 → 1.0.153

package/README.md

@@ -12,14 +12,14 @@
 <a href="https://github.com/toolsdk-ai/toolsdk-mcp-registry/actions/workflows/test.yaml">
   <img src="https://github.com/toolsdk-ai/toolsdk-mcp-registry/actions/workflows/test.yaml/badge.svg" alt="Build Status" />
 </a>
-<img src="https://img.shields.io/badge/MCP_Servers-4520-blue?style=flat-square" alt="MCP Servers Count" />
+<img src="https://img.shields.io/badge/MCP_Servers-4521-blue?style=flat-square" alt="MCP Servers Count" />
 <img src="https://img.shields.io/badge/LICENSE-MIT-ff69b4?style=flat-square" alt="License" />
 <br />
 <a href="https://www.producthunt.com/products/toolsdk-ai">
   <img src="https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=997428&theme=light&period=daily" alt="Product Hunt" height="40" />
 </a>
 
-<a href="#mcp-servers">🔍 <b>Browse 4520+ Tools</b></a>
+<a href="#mcp-servers">🔍 <b>Browse 4521+ Tools</b></a>
 &nbsp;&nbsp;•&nbsp;&nbsp;
 <a href="#quick-start">🐳 <b>Self-hosted</b></a>
 &nbsp;&nbsp;•&nbsp;&nbsp;
@@ -75,7 +75,7 @@ docker compose up -d
 - *See [Configuration Guide](./docs/DEVELOPMENT.md) for full details.*
 
 > [!TIP]
-> **Tip for Private Deployment**: This registry contains 4520+ public MCP servers. If you only need a specific subset for your private environment, you can prune the `packages/` directory.
+> **Tip for Private Deployment**: This registry contains 4521+ public MCP servers. If you only need a specific subset for your private environment, you can prune the `packages/` directory.
 > 📖 See [Package Management Guide](./docs/DEVELOPMENT.md#5--package-management-for-private-deployment) for details.
 
 That's it! Your self-hosted MCP registry is now running with:
@@ -87,7 +87,7 @@ That's it! Your self-hosted MCP registry is now running with:
 
 - 🌐 **Local Web Interface**: http://localhost:3003
 - 📚 **Swagger API Docs**: http://localhost:3003/swagger  
-- 🔍 **Search & Execute** 4520+ MCP Servers remotely
+- 🔍 **Search & Execute** 4521+ MCP Servers remotely
 - 🤖 **Integrate** with your AI agents, chatbots, and LLM applications
 
 #### 🌐 Remote Tool Execution Example
@@ -221,7 +221,7 @@ graph TD
 
 This open-source project provides:
 
-- **Structured Registry** - 4520+ MCP servers with metadata
+- **Structured Registry** - 4521+ MCP servers with metadata
 - **Unified Gateway** - HTTP API to query and execute tools remotely
 - **Auto-Generated Docs** - Always up-to-date README and API documentation
 
@@ -320,12 +320,12 @@ Your MCP server will be:
 
 ## MCP Servers Directory
 
-**4520+ AI Agent Tools, LLM Integrations & Automation Servers**
+**4521+ AI Agent Tools, LLM Integrations & Automation Servers**
 
 > [!NOTE]
 > ⭐ **Featured below**: Hand-picked, production-ready MCP servers verified by our team.
 >
-> 📚 **Looking for all 4520+ servers?** Check out [**All MCP Servers**](./docs/ALL-MCP-SERVERS.md) for the complete list.
+> 📚 **Looking for all 4521+ servers?** Check out [**All MCP Servers**](./docs/ALL-MCP-SERVERS.md) for the complete list.
 
 > [!TIP]
 > If a package is marked as `validated: true` in the index, you can usually wire it up in minutes via ToolSDK (e.g. `getAISDKTool(toolKey)`).
@@ -859,6 +859,7 @@ Enhance your development workflow with tools for coding and environment manageme
 - [✅ mcp-server-tree-sitter](https://github.com/wrale/mcp-server-tree-sitter): Provides code analysis capabilities through tree-sitter parsing, enabling structured understanding and manipulation of source code across multiple programming languages for tasks like code review, refactoring, and documentation generation.  (26 tools) (python) 
 - [✅ mcp-svelte-docs](https://github.com/spences10/mcp-svelte-docs): Integrates with Svelte documentation to enable efficient querying and retrieval of framework-specific content for development assistance.  (12 tools) (node) 
 - [✅ metatag-genie](https://github.com/terryso/meta_tag_genie): Enables AI to write standardized metadata to various image file formats including HEIC and PNG for automated tagging, photo organization, and copyright embedding without switching contexts.  (1 tools) (node) 
+- [✅ project-mcp](https://github.com/pouyanafisi/project-mcp): AI-native project management with intent-based documentation search, Jira-like task IDs (PROJECT-001), backlog workflow (import → promote → archive), thought processing (brain dumps → structured tasks with intent analysis), and project file management. (40 tools, 12 prompts)  (42 tools) (node) 
 - [✅ qasphere-mcp](https://github.com/hypersequent/qasphere-mcp): Integration with QA Sphere test management system, enabling LLMs to discover, summarize, and interact with test cases directly from AI-powered IDEs.  (6 tools) (node) 
 - [✅ sf-mcp](https://github.com/codefriar/sf-mcp): Exposes Salesforce CLI functionality for interacting with Salesforce orgs, enabling developers to query data, deploy code, and manage orgs through dynamically discovered commands.  (5 tools) (node) 
 - [✅ shadow-cljs-mcp](https://github.com/bigsy/shadow-cljs-mcp): Monitors ClojureScript builds in real-time, providing detailed status information including compilation status, warnings, errors, and file-specific details for verifying build success after code changes.  (1 tools) (node) 

package/indexes/categories-list.json

@@ -2291,6 +2291,7 @@
       "forge",
       "docker-mcp",
       "@magicuidesign/mcp",
+      "project-mcp",
       "mcpdoc",
       "freecad-mcp",
       "mcp-maker",

package/indexes/packages-list.json

@@ -56087,5 +56087,180 @@
     "path": "uncategorized/toolsdk-remote-ai-dynamicendpoints-m365-core-mcp.json",
     "validated": false,
     "tools": {}
+  },
+  "project-mcp": {
+    "category": "developer-tools",
+    "path": "developer-tools/project-mcp.json",
+    "validated": true,
+    "tools": {
+      "search_project": {
+        "name": "search_project",
+        "description": "Search across project sources with smart intent detection. IMPORTANT: \"project docs\" means APPLICATION documentation (docs/ + DECISIONS.md), NOT project management. Use intent \"project_docs\" when user says \"project docs/documents/documentation\" to search application documentation. Use intent \"plan\" for project management (status, todos, roadmap, backlog)."
+      },
+      "search_docs": {
+        "name": "search_docs",
+        "description": "Search only the docs/ directory for reference documentation. Use this when the user specifically asks for \"docs\" or \"documentation\". Returns relevant documentation chunks with file paths and content snippets."
+      },
+      "get_doc": {
+        "name": "get_doc",
+        "description": "Get the full content of a specific file. Supports files from .project/, root-level, or docs/. Use the path as returned from search results."
+      },
+      "list_docs": {
+        "name": "list_docs",
+        "description": "List all available documentation files organized by category. Use this to discover what documentation is available or to get an overview of the documentation structure."
+      },
+      "get_doc_structure": {
+        "name": "get_doc_structure",
+        "description": "Get the complete documentation directory structure with file paths and descriptions. Useful for understanding the organization of documentation."
+      },
+      "manage_project_file": {
+        "name": "manage_project_file",
+        "description": "Smart tool that automatically determines which project file to create or update based on context. Use this when making changes to the project - it will check project state and determine if index.md, ROADMAP.md, TODO.md, STATUS.md, or DECISIONS.md should be created/updated. This is the primary tool for managing project documentation during development."
+      },
+      "check_project_state": {
+        "name": "check_project_state",
+        "description": "Checks the current state of project management files. Returns which files exist (.project/index.md, ROADMAP.md, TODO.md, STATUS.md, DECISIONS.md) and provides a summary of project state. Use this before making changes to understand what exists."
+      },
+      "create_or_update_roadmap": {
+        "name": "create_or_update_roadmap",
+        "description": "Creates or updates the ROADMAP.md file in .project/ directory. Use this when planning future work, milestones, or phases. If the file exists, intelligently merges new content with existing roadmap."
+      },
+      "create_or_update_todo": {
+        "name": "create_or_update_todo",
+        "description": "Creates or updates the TODO.md file in .project/ directory. Use this when adding tasks, marking items complete, or updating task status. Intelligently organizes tasks into sections (In Progress, Next Up, Blocked, Completed)."
+      },
+      "create_or_update_status": {
+        "name": "create_or_update_status",
+        "description": "Creates or updates the STATUS.md file in .project/ directory. Use this when updating project health, recent changes, metrics, or current phase. Automatically updates the \"Last Updated\" timestamp."
+      },
+      "create_or_update_index": {
+        "name": "create_or_update_index",
+        "description": "Creates or updates the index.md file in .project/ directory. This is the contract file that defines how agents should interpret sources. Use this when setting up project structure or updating source mappings."
+      },
+      "create_or_update_decisions": {
+        "name": "create_or_update_decisions",
+        "description": "Creates or updates the DECISIONS.md file in .project/ directory. Use this when documenting architecture decisions, trade-offs, or rationale. Helps maintain a decision log for the project."
+      },
+      "add_decision": {
+        "name": "add_decision",
+        "description": "Adds a single architecture decision record (ADR) to DECISIONS.md. Creates a structured entry with title, context, decision, and consequences sections."
+      },
+      "list_decisions": {
+        "name": "list_decisions",
+        "description": "Lists all architecture decisions from DECISIONS.md with optional filtering by status or tag."
+      },
+      "update_project_status": {
+        "name": "update_project_status",
+        "description": "Quick status update for the project. Adds a timestamped entry to STATUS.md with the current status, changes, or notes."
+      },
+      "add_roadmap_milestone": {
+        "name": "add_roadmap_milestone",
+        "description": "Adds a milestone or phase to ROADMAP.md. Creates a structured entry with title, description, target date, and deliverables."
+      },
+      "get_decision": {
+        "name": "get_decision",
+        "description": "Reads a specific architecture decision by ADR ID. Returns the full decision content including context, decision, and consequences."
+      },
+      "get_roadmap": {
+        "name": "get_roadmap",
+        "description": "Reads the current roadmap content from ROADMAP.md. Returns milestones, phases, and planned work."
+      },
+      "create_task": {
+        "name": "create_task",
+        "description": "Creates a new task with YAML frontmatter metadata. Uses Jira-like IDs (e.g., AUTH-001, API-042) for stable references. Supports dependencies, priorities, estimates, due dates, and tags. Agents can determine execution order by checking dependencies and priorities."
+      },
+      "update_task": {
+        "name": "update_task",
+        "description": "Updates an existing task by ID. Can update any field including status, priority, owner, dependencies, etc. Use this to transition tasks through workflow states."
+      },
+      "get_task": {
+        "name": "get_task",
+        "description": "Reads and returns a specific task by ID. Shows all metadata including frontmatter, description, subtasks, and notes."
+      },
+      "delete_task": {
+        "name": "delete_task",
+        "description": "Permanently deletes a task from todos/. Use with caution - this cannot be undone. Consider using archive_task instead for completed tasks."
+      },
+      "get_next_task": {
+        "name": "get_next_task",
+        "description": "Returns the next task(s) that should be worked on. Considers: dependencies (only returns tasks whose dependencies are done), priority (P0 first), status (excludes done/blocked), and optionally filters by owner or project. This is the key tool for agentic execution - call this to know what to do next."
+      },
+      "list_tasks": {
+        "name": "list_tasks",
+        "description": "Lists all tasks with optional filtering. Returns a summary view of tasks organized by status and priority."
+      },
+      "search_tasks": {
+        "name": "search_tasks",
+        "description": "Search tasks by keyword in title, description, or content. Returns matching tasks with relevance ranking."
+      },
+      "sync_todo_index": {
+        "name": "sync_todo_index",
+        "description": "Syncs the parent TODO.md file with all tasks. Generates a dashboard view with tasks organized by status, priority counts, dependency graph, and execution order. This provides a bird's eye view of all work."
+      },
+      "import_tasks": {
+        "name": "import_tasks",
+        "description": "Parses a plan document and imports tasks to BACKLOG.md (not individual files). Use this to populate the backlog from a roadmap or requirements doc. Tasks stay in BACKLOG until promoted to active work via promote_task."
+      },
+      "promote_task": {
+        "name": "promote_task",
+        "description": "Promotes a task from BACKLOG.md to an active YAML task file in todos/. Use this when starting work on a backlog item. Creates a full task file with YAML frontmatter, dependencies, and metadata."
+      },
+      "archive_task": {
+        "name": "archive_task",
+        "description": "Archives a completed task by moving it from todos/ to archive/. Keeps the active task queue small and focused. Archived tasks are preserved for history but excluded from get_next_task."
+      },
+      "add_to_backlog": {
+        "name": "add_to_backlog",
+        "description": "Adds a single item to BACKLOG.md. Use this for quick task creation without bulk import. Items are added to the specified priority section and can later be promoted to active work."
+      },
+      "get_backlog": {
+        "name": "get_backlog",
+        "description": "Reads and returns the current backlog contents with optional filtering. Shows tasks organized by priority with counts and summary."
+      },
+      "update_backlog_item": {
+        "name": "update_backlog_item",
+        "description": "Updates an item in BACKLOG.md. Can change priority, title, tags, or phase without promoting to active work."
+      },
+      "remove_from_backlog": {
+        "name": "remove_from_backlog",
+        "description": "Removes an item from BACKLOG.md without promoting it. Use for tasks that are no longer needed or were added by mistake."
+      },
+      "list_archived_tasks": {
+        "name": "list_archived_tasks",
+        "description": "Lists tasks in the archive/ directory. Shows completed work history with optional filtering by project or date."
+      },
+      "unarchive_task": {
+        "name": "unarchive_task",
+        "description": "Restores a task from archive/ back to todos/ for further work. Use when a completed task needs to be reopened."
+      },
+      "lint_project_docs": {
+        "name": "lint_project_docs",
+        "description": "Validates project documentation against standards. Checks for required files, valid frontmatter, broken dependencies, missing fields, and formatting issues. Can auto-fix common problems. Run this before commits to ensure documentation quality."
+      },
+      "init_project": {
+        "name": "init_project",
+        "description": "Initializes the .project/ directory with all standard files following strict templates. Creates index.md (contract), TODO.md (dashboard), BACKLOG.md (prioritized work queue), ROADMAP.md, STATUS.md, DECISIONS.md, and todos/ directory. Use this to bootstrap a new project with proper structure."
+      },
+      "process_thoughts": {
+        "name": "process_thoughts",
+        "description": "Reads brain dump markdown files from .project/thoughts/todos/ and returns the content along with project context for analysis.\n\nThis tool gathers:\n1. **Raw thought content** - The unstructured brain dump as written\n2. **Project context** - Existing tasks, roadmap milestones, decisions for reference\n3. **Task format guide** - The YAML structure for creating tasks\n\nYOU (the LLM) should then analyze the content to:\n- Understand the user's intent (explicit, shadow/underlying, practical)\n- Identify logical task groupings (consolidate related items)\n- Determine appropriate priorities based on context\n- Create well-structured tasks using create_task\n- **After creating tasks, use archive_thought to archive the processed file**\n\nThe tool does NOT automatically create tasks - it provides you with everything needed to make intelligent decisions about task creation."
+      },
+      "archive_thought": {
+        "name": "archive_thought",
+        "description": "Archives a processed thought file by moving it to .project/thoughts/todos/.archive/. \nUse this after you've created tasks from a thought file to keep the active thoughts folder clean.\nAlso logs the archive action with timestamp and created task IDs."
+      },
+      "list_thoughts": {
+        "name": "list_thoughts",
+        "description": "Lists all thought files in the .project/thoughts/ directory structure. Shows available brain dump files organized by category."
+      },
+      "list_archived_thoughts": {
+        "name": "list_archived_thoughts",
+        "description": "Lists all archived thought files with their processing history. Shows what thoughts were processed, when, and what tasks were created."
+      },
+      "get_thought": {
+        "name": "get_thought",
+        "description": "Reads a specific thought file and returns its raw content for review."
+      }
+    }
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@toolsdk.ai/registry",
-  "version": "1.0.151",
+  "version": "1.0.153",
   "description": "An Open, Structured, and Standard Registry for MCP Servers and Packages.",
   "keywords": [
     "mcp",
@@ -667,6 +667,7 @@
     "pokemon-vgc-calc-mcp": "0.1.0",
     "powerplatform-mcp": "0.4.5",
     "productboard-mcp": "1.0.1",
+    "project-mcp": "3.3.0",
     "promptopia-mcp": "1.1.0",
     "proofly-mcp": "1.2.3",
     "pulsemcp-server": "0.1.2",

package/packages/developer-tools/project-mcp.json

@@ -0,0 +1,15 @@
+{
+  "type": "mcp-server",
+  "name": "Project MCP",
+  "packageName": "project-mcp",
+  "description": "AI-native project management with intent-based documentation search, Jira-like task IDs (PROJECT-001), backlog workflow (import → promote → archive), thought processing (brain dumps → structured tasks with intent analysis), and project file management. (40 tools, 12 prompts)",
+  "url": "https://github.com/pouyanafisi/project-mcp",
+  "runtime": "node",
+  "license": "MIT",
+  "env": {
+    "DOCS_DIR": {
+      "description": "Path to documentation directory (default: ./docs)",
+      "required": false
+    }
+  }
+}