Skip to main content
Glama
brnbio

Project Planner MCP

by brnbio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
inspectA

Scannt das aktuelle Laravel-Projekt und erfasst den IST-Zustand.

Analysiert:

  • Models und deren Relations

  • Migrations (Datenbankstruktur)

  • Controllers und deren Methods

  • Routes

  • Vue Pages und Components

Fragt dann nach:

  • Aktueller Stand aus deiner Sicht

  • Zielzustand (was soll erreicht werden)

Output: project_context.json

planA

Erstellt Tickets basierend auf dem project_context.

Analysiert:

  • Gap zwischen IST und SOLL

  • Benötigte Änderungen an DB, Backend, Frontend

  • Dependencies zwischen Tasks

Generiert Tickets mit:

  • 4h oder 8h Schätzung

  • Labels (Backend, Frontend, Testing, Database)

  • Technische Checkliste

  • Betroffene Dateien/Pfade

Output: tickets_draft.json

exportA

Exportiert die finalen Tickets als JSON.

Zeigt nochmal die Übersicht und fragt nach Bestätigung/Änderungen.

Output: tickets_final.json im Projektverzeichnis

Prompts

Interactive templates invoked by user choice

NameDescription
project:inspectProjekt analysieren und IST/SOLL-Zustand erfassen
project:planTickets basierend auf dem Projekt-Context generieren
project:exportFinale Tickets als JSON exportieren

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct phase: inspect captures the current state, plan creates tickets from that context, and export finalizes them. No overlap in purpose; they form a clear sequence.

Naming Consistency5/5

All tool names are single-word verbs in lowercase (inspect, plan, export), following a consistent imperative style. The naming clearly indicates the action each performs.

Tool Count5/5

With only 3 tools, the set is tightly scoped to the planning workflow. Each tool is necessary and the pipeline is complete without unnecessary extras.

Completeness5/5

The tools cover the entire lifecycle from analyzing the project to generating and exporting tickets. The export tool also handles confirmation/changes, closing the loop with no obvious gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources