
Railagent
from railwave-labs
Provides structured workflows and tools for AI agents working with software development projects, with a specialized focus on Rails applications.
Railagent - MCP Server for AI Agent Workflows
A Model Context Protocol (MCP) server that provides structured workflows and tools for AI agents working with software development projects, with specialized focus on Rails applications.
What This Does
Railagent provides AI agents with a comprehensive workflow system for software development. It guides agents through the entire development lifecycle from requirements gathering to implementation, ensuring consistent and high-quality outcomes.
How It Works
For New Projects
- Functional Requirements: Use the functional requirements tool to collect necessary information about the project (purpose, users, capabilities, workflows, context, edge cases)
- Product Requirements Document (PRD): Generate a complete PRD from the functional requirements, breaking down the project into features and user stories
- Feature Requirements Document (FRD): For each feature, create a detailed FRD that breaks large features into individual PR-sized units
- Task Design Document (TDD): Transform the FRD into an implementation plan with specific subtasks, where each subtask corresponds to a commit
For Existing/Complex Systems
- Skip directly to step 4 (TDD) above when you have a clear understanding of what needs to be built
Implementation Workflow
- Initialize Tasks: Call the initialize tool to set up subtasks based on your TDD implementation plan (stored in
.cursor/scratch/tasks/) - Execute Tasks: Use the execute tool to work on each task individually. Each task represents exactly one commit, and the agent waits for review before committing
- Track Progress: Progress is maintained in
.cursor/scratch/todo.mdwith notes and status updates
All documents and tasks are automatically stored in the .cursor/scratch/ folder for easy access and organization.
Available Tools
Documentation Tools
- build_functional_requirements: Collects comprehensive project requirements
- build_prd: Generates Product Requirements Documents from functional requirements
- build_frd: Creates Feature Requirements Documents for specific features
- build_tdd: Breaks down features into detailed implementation plans with commit-level subtasks
- build_architecture: Generates comprehensive architecture documentation
Workflow Tools
- initialize_task: Sets up implementation subtasks from TDD plans
- execute_task: Executes individual tasks with review checkpoints
Project Structure
railagent/
โโโ app.rb # Main application entry point
โโโ lib/ # Tool implementations
โ โโโ docs/ # Documentation tools
โ โโโ workflow/ # Workflow management tools
โโโ prompts/ # Workflow prompts and templates
โ โโโ docs/ # Documentation workflow prompts
โ โโโ workflow/ # Implementation workflow templates
โโโ Dockerfile # Docker configuration
โโโ Gemfile # Ruby dependencies
โโโ README.md # This fileDevelopment
Using the Pre-built Image
The easiest way to use Railagent is with the pre-built Docker image:
docker run -i --rm cestbalez/railagent:latestLocal Development
If you want to contribute or modify the code:
git clone <your-repo-url>
cd railagent
bundle install
ruby app.rbBuilding Your Own Image
git clone <your-repo-url>
cd railagent
docker build -t railagent .docker run -i --rm cestbalez/railagent:latestSetup Instructions
1. Configure MCP Client
Add to your mcp.json file:
{
"mcpServers": {
"Railagent": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"cestbalez/railagent:latest"
]
}
}
}2. Restart Your MCP Client
Restart your MCP client to load the new server.
Note: The Docker image will be automatically pulled from DockerHub on first use. No manual installation or repository cloning required!
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under MITโ you can use, modify, and redistribute it under that license's terms.
License
This project is licensed under the terms specified in the LICENSE file.