Skip to main content
Glama
g-hyeong

aidflow

by g-hyeong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AIDFLOW_ROOTNoRoot path for the project. Defaults to process.cwd() if not set.

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
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
initA

Initialize aidflow in the current project.

Creates .aidflow/ directory, config, guides, and Claude Code skills (.claude/skills/). Call this once when first using aidflow in a project. If already initialized, returns current status (use force: true to overwrite).

sessionA

Manage development sessions. (create/list/status/complete)

  • create: Start a new session. Optionally creates a git worktree for isolation.

  • list: Show all active sessions with their status.

  • status: Get session progress (changed files, plan progress, next suggestion).

  • complete: Archive session to history. Prompts for worktree cleanup.

Start with create when beginning work, end with complete when done.

planA

Manage session work plans. (create/get)

  • create: Start a structured planning workflow. Guides through requirements gathering (HITL via AskUserQuestion), codebase research, and writing a comprehensive plan.md (PRD + implementation plan). The plan serves as the final execution specification before coding.

  • get: Read existing plan and show progress (checkbox-based).

Optional - skip for simple bug fixes. Use for medium/large tasks that benefit from upfront planning.

guideA

Access project guide documents. (list/read)

  • list: Show available guides (excludes _-prefixed required guides).

  • read: Read a specific guide by topic name.

Required guides (_plan.md, _session_*.md, etc.) are auto-loaded by corresponding tools. Regular guides: When a guide name matches the current task context, proactively read it without waiting for the user to ask.

select_serviceA

Select target service in multi-service workspace. (list/select/status)

  • list: Discover all .aidflow directories in workspace. Auto-selects if only one found.

  • select: Select a specific service by name. Optionally bind to a session for parallel work.

  • status: Show current service selection (session-bound or global).

Call this before other tools (session, plan, guide) when working in a multi-service workspace. Single-service projects are auto-selected on list.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

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.4/5.0

Scored across 5 tools

Disambiguation5/5

All five tools have clearly distinct purposes: guide for reading documents, init for project setup, plan for work plans, select_service for multi-service selection, and session for development sessions. No overlap in functionality.

Naming Consistency4/5

Most tool names are single lowercase verbs (guide, init, plan, session), which is consistent. However, 'select_service' breaks this pattern by using an underscore and a verb_noun structure, creating minor inconsistency.

Tool Count5/5

With 5 tools, the server is well-scoped. Each tool addresses a core aspect of the development workflow without being too numerous or too sparse.

Completeness4/5

The tool set covers the main lifecycle (init, plan, session, guide reading) with appropriate actions. Minor gaps like no explicit update for plans or deselect for service are acceptable for the domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources