Pathfinder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATHFINDER_HOST | No | SSE server host | 127.0.0.1 |
| PATHFINDER_PORT | No | SSE server port | 8080 |
| PATHFINDER_TRANSPORT | No | Transport: stdio or sse | stdio |
| PATHFINDER_MAX_TOKENS | No | Max context tokens | 128000 |
| PATHFINDER_SESSIONS_DIR | No | Session storage path | ~/.pathfinder-sessions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkC | Check server health and return status. |
| start_researchC | Start a new research session. Args: task_description: Description of the task to research session_id: Optional session ID (auto-generated if not provided) |
| save_researchC | Save research findings to the session. Args: session_id: Session ID findings: Research findings to save |
| start_planA | Transition from research to plan phase. Creates plan.md template. Requires research to be complete. Args: session_id: Session ID |
| save_planB | Save implementation plan. Validates plan follows Cursor plan format with YAML frontmatter. Args: session_id: Session ID plan_content: Plan content in Cursor plan format |
| implement_phaseB | Execute an implementation phase from the plan. Args: session_id: Session ID phase_number: Specific phase to execute (defaults to next uncompleted) |
| compact_contextB | Compress session context into summary artifacts. Use when context utilization exceeds 60%. Args: session_id: Session ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generate_plan_from_research | Generate an implementation plan from research findings. Args: session_id: Session ID with completed research |
| compact_session | Generate a compressed session summary. |
| resume_session | Generate context to resume a session. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| research_template | Research phase markdown template. |
| plan_template | Plan phase markdown template. |
| implementation_checklist | Implementation verification checklist template. |
| progress_template | Progress tracking markdown template. |
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: health_check, compact_context, save_research, start_research, start_plan, save_plan, and implement_phase each target different phases or actions in a workflow. However, save_research and save_plan could be slightly confused as both involve saving content, but their descriptions clarify they handle different types of data (research findings vs. implementation plans).
The naming follows a consistent verb_noun pattern throughout (e.g., compact_context, health_check, implement_phase, save_plan, save_research, start_plan, start_research), which is predictable and readable. There are no deviations in style or convention, making it easy for agents to understand the action each tool performs.
With 7 tools, the count is well-scoped for a server focused on managing research and implementation workflows. Each tool appears to earn its place by covering distinct steps in the process, from starting research to executing phases, without being overly sparse or bloated.
The tool set covers key phases like research, planning, and implementation, but there are notable gaps. For example, there are no tools for updating or deleting saved plans or research, and operations like reviewing or listing existing sessions are missing. This could lead to dead ends for agents trying to manage ongoing work comprehensively.