home / mcp / ai naming standard mcp server
AI-driven development naming convention. Standard file naming rules and patterns for automated code generation by AI systems.
Configuration
View docs{
"mcpServers": {
"ai-naming-standard-mcp": {
"command": "node",
"args": [
"path/to/ai-naming-standard-mcp/src/index.js"
]
}
}
}The AI File Naming Assistant is a multi-AI MCP server that standardizes how you name files across your project. It helps ensure clarity, consistency, and better AI understanding by producing descriptive, production-ready file names that encode role, layer, action, and environment.
You use the server by connecting an MCP client to the provided MCP endpoint and letting the client generate file names as you describe your intention. Tell the AI what you want to create, and it will respond with a standardized file name like 001_FE_User-Login_C_Page_PROD.jsx. The system supports orchestration across multiple AIs so that one writes, another reviews, and a third designs the structure, all following the same naming rules.
When you want to name new or updated files, describe the goal in plain language, for example: "Create a login page" or "Add a payment API." The server translates your intent into a consistent, production-ready file name that encodes sequence number, layer, feature, action, and environment.
Prerequisites: Node.js (version 16 or newer) and a modern JavaScript runtime. You also need npm or yarn installed.
npm install -g ai-naming-standard-mcpStart by configuring your MCP client to connect to the server. A common stdio-based config shown in usage examples uses node to run the MCP script.
{
"mcpServers": {
"ai-naming-standard": {
"command": "node",
"args": ["path/to/ai-naming-standard-mcp/src/index.js"]
}
}
}- Use plain language prompts to describe the desired file. The system encodes the file name with a prefix number, layer codes, and environment tags to create a predictable naming scheme.
- Maintain consistency across teams by following the same naming format for all new files, updates, migrations, and tests.
A typical resulting file name might look like: 001_FE_User-Login_C_Page_PROD.jsx. The segments indicate: file number, frontend layer, feature, action, page type, and production environment.
Another example: 003_DB_Order-Schema_C_Migration_PROD.sql indicates a database migration creating an order table for production.