project-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y project-mcp@3.3.0
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 5 returned a result.
list_docs | Returned a result under 0.1 s · 29 characters |
get_doc_structure | Returned a result under 0.1 s · 33 characters |
list_decisions | Returned a result under 0.1 s · 83 characters |
get_roadmap | Returned a result under 0.1 s · 96 characters |
get_next_task | Returned a result under 0.1 s · 165 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
1 tool with commands in capitals or very long text
- Gives the agent orders in
search_project:Search across project sources with smart intent detection. IMPORTANT: "project docs" means APPLICATION documentation (docs/ + DECISIONS.md), NOT project management. Use
Common and usually harmless: it is how many makers stress how a tool should be used.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
search_project query, intent, maxResults
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 query, category, maxResults
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 path
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 category
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
Get the complete documentation directory structure with file paths and descriptions. Useful for understanding the organization of documentation.
37 more tools
manage_project_file action, content, fileType
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
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 content, section, replace
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 content, section, markComplete, replace
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 content, updateType, replace
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 content, replace
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 content, decisionTitle, replace
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 title, context, decision, consequences, status, tags
Adds a single architecture decision record (ADR) to DECISIONS.md. Creates a structured entry with title, context, decision, and consequences sections.
list_decisions status, tag
Lists all architecture decisions from DECISIONS.md with optional filtering by status or tag.
update_project_status status, health, changes, blockers, next_milestone
Quick status update for the project. Adds a timestamped entry to STATUS.md with the current status, changes, or notes.
add_roadmap_milestone title, description, target_date, deliverables, status
Adds a milestone or phase to ROADMAP.md. Creates a structured entry with title, description, target date, and deliverables.
get_decision id
Reads a specific architecture decision by ADR ID. Returns the full decision content including context, decision, and consequences.
get_roadmap section
Reads the current roadmap content from ROADMAP.md. Returns milestones, phases, and planned work.
create_task title, project, description, owner, priority, status, depends_on, blocked_by, estimate, due, tags, subtasks
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 id, title, description, owner, priority, status, depends_on, blocked_by, estimate, due, tags, add_subtask, complete_subtask
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 id
Reads and returns a specific task by ID. Shows all metadata including frontmatter, description, subtasks, and notes.
delete_task id, confirm
Permanently deletes a task from todos/. Use with caution - this cannot be undone. Consider using archive_task instead for completed tasks.
get_next_task owner, project, include_blocked, limit
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 project, owner, status, priority, tag
Lists all tasks with optional filtering. Returns a summary view of tasks organized by status and priority.
search_tasks query, project, status, include_archived, limit
Search tasks by keyword in title, description, or content. Returns matching tasks with relevance ranking.
sync_todo_index format
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 source, source_type, project, phase, default_priority, dry_run
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 task_id, owner, priority, depends_on, estimate, due
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 task_id, force
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 title, project, priority, tags, phase, subtasks
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 priority, project, include_promoted
Reads and returns the current backlog contents with optional filtering. Shows tasks organized by priority with counts and summary.
update_backlog_item task_id, title, priority, tags, phase
Updates an item in BACKLOG.md. Can change priority, title, tags, or phase without promoting to active work.
remove_from_backlog task_id, reason
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 project, limit
Lists tasks in the archive/ directory. Shows completed work history with optional filtering by project or date.
unarchive_task task_id, status
Restores a task from archive/ back to todos/ for further work. Use when a completed task needs to be reopened.
lint_project_docs fix, strict, scope
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 project_name, project_description, overwrite
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 file, project
Reads brain dump markdown files from .project/thoughts/todos/ and returns the content along with project context for analysis. This tool gathers: 1. **Raw thought content** - The unstructured brain dump as written 2. **Project context** - Existing tasks, roadmap milestones, decisions for reference 3. **Task format guide** - The YAML structure for creating tasks YOU (the LLM) should then analyze the content to: - Understand the user's intent (explicit, shadow/underlying, practical) - Identify logical task groupings (consolidate related items) - Determine appropriate priorities based on context - Create well-structured tasks using create_task - **After creating tasks, use archive_thought to archive the processed file** The tool does NOT automatically create tasks - it provides you with everything needed to make intelligent decisions about task creation.
archive_thought file, created_tasks, notes
Archives a processed thought file by moving it to .project/thoughts/todos/.archive/. Use this after you've created tasks from a thought file to keep the active thoughts folder clean. Also logs the archive action with timestamp and created task IDs.
list_thoughts category, include_archived
Lists all thought files in the .project/thoughts/ directory structure. Shows available brain dump files organized by category.
list_archived_thoughts limit
Lists all archived thought files with their processing history. Shows what thoughts were processed, when, and what tasks were created.
get_thought file, category, from_archive
Reads a specific thought file and returns its raw content for review.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18.0.0 |
| Source | github.com/pouyanafisi/project-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-nMsVfIcWIgM+oRco+B+FiNT8ME4X8HMvMIWLIQREV2LxPtECFyk50JJWR0Au47ycHLoEVzN5JpilCTwcaKRSFw== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/project-mcp)
New version out? Ask for a fresh report.