A
licenseNot graded
qualityD
maintenanceAI-powered MCP server that enables Claude and other LLMs to interact directly with construction documents, drawings, and specifications through advanced RAG and hybrid search capabilities.
9
MIT
MCP Spec Generator
by Huxley-Brown
This server generates project specifications from text prompts and creates MCP create_file/edit_file proposals. You can optionally write the proposed files directly to disk by setting allowWrite=true.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Spec Generatorcreate a retro arcade game with HTML, CSS, and vanilla JavaScript"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
retro-arcade\n\nMinimal static HTML/CSS/JS project that runs locally without build tools. Features a retro landing page and a lightweight Vampire Survivors-like canvas game.\n\nHow to run\n- Option A: Open index.html directly in your browser (double-click the file).\n- Option B: Serve with a simple local HTTP server and open http://localhost:8000:\n - Python 3: python3 -m http.server\n - Node (if installed): npx http-server .\n\nFiles\n- index.html: Landing page with full-viewport layout, retro font, centered Play overlay that starts the game.\n- styles.css: Retro aesthetic (dark gradient, subtle CRT scanlines, neon button, responsive canvas).\n- game.js: Pure vanilla JS game loop (no dependencies), DPR-aware canvas, input, enemies, projectiles, collisions, HUD, and game states.\n- specs/overview.md: Project overview.\n- specs/tasks.md: MVP tasks checklist.\n- specs/task-requirements.md: Functional and non-functional requirements.\n- specs/task-gameplay.md: Gameplay loop and AI notes.\n\nGameplay overview\n- Press Play to hide the overlay and start immediately.\n- You control a circular player, enemies spawn from screen edges and seek you.\n- Every 500ms an auto-attack fires toward the nearest enemy (mild homing); projectiles expire on hit or after a short lifetime.\n- Score increases on enemy kills. HUD shows score, HP, and elapsed time.\n- When HP reaches 0, a Game Over overlay appears with a Restart button.\n\nControls\n- Move: WASD or Arrow Keys\n- There is no manual fire; attacks are automatic.\n\nTech and browser support\n- No frameworks or build tools required; works in evergreen browsers.\n- Uses requestAnimationFrame with a clamped delta for stability.\n- Canvas is scaled for devicePixelRatio and resizes with the window.\n\nPerformance tips\n- Close other heavy tabs for best performance.\n- If your device has a very high DPR, zooming out (or reducing system scaling) can improve frame rate.\n\nCustomization\n- Tweak speeds, spawn rates, colors, and sizes in game.js constants to adjust difficulty and feel.\n
Available Tools
1 toolgenerate_projectC
Generate a project spec and return MCP create_file/edit_file proposals. Set allowWrite=true to write files.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| prompt | Yes | ||
| allowWrite | No |
TDQS
C2.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses that the tool returns MCP create_file/edit_file proposals and requires 'allowWrite=true' for writing files, adding some behavioral context. However, it doesn't cover aspects like rate limits, error handling, or what happens if 'allowWrite' is false, leaving gaps in transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief and front-loaded, stating the main action in the first part. Both sentences are relevant, with no wasted words, making it efficient. However, it could be slightly more structured to separate purpose from usage instructions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on the generated project spec's format, what the proposals entail, error conditions, or return values. For a tool with two parameters and behavioral complexity, this leaves significant gaps in understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It explains that 'allowWrite' controls file writing, adding meaning beyond the schema. However, it doesn't describe the 'prompt' parameter's purpose or format, leaving one of the two parameters undocumented. This partial compensation is insufficient for full clarity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool generates a project spec and returns MCP proposals, which provides a basic purpose. However, it's somewhat vague about what a 'project spec' entails and doesn't specify the format or content of the generated spec. No sibling tools exist for comparison, so differentiation isn't applicable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions setting 'allowWrite=true to write files,' which implies usage for file creation, but provides no guidance on when to use this tool versus alternatives or any prerequisites. It lacks explicit when/when-not instructions or context for appropriate use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- First observed
generate_project
TDQS
C2.9/5.0
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_project' has a clearly defined and distinct purpose.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern ('generate_project'), and with only one tool, consistency is inherently perfect as there are no other tools to compare against.
Tool Count2/5
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a 'MCP Spec Generator', one tool feels thin and may not cover potential variations or related operations, such as updating or validating specs.
Completeness2/5
The server's purpose appears to be generating project specs, but with only a 'generate_project' tool, there are significant gaps. Missing operations likely include updating existing specs, validating specs, or listing generated projects, which could cause agent failures in broader workflows.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Use AI models for chat, image, and video generation from Claude Code and other MCP hosts.
MCP server for generating rough-draft project plans from natural-language prompts.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Connect Claude AI to UluP Spaces via MCP — create projects, nodes, and tasks with OAuth 2.0.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceA comprehensive, domain-agnostic documentation scraping and AI integration toolkit. Scrape any documentation website, create structured databases, and integrate with Claude Desktop via MCP (Model Context Protocol) for seamless AI-powered documentation assistance.5-
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI assistants like Claude to interact with Autodesk Construction Cloud Build platform for construction project management, including issues tracking, RFIs, submittals, and document management through natural language.-
- AlicenseBqualityDmaintenanceConnects Blender to Claude AI through the Model Context Protocol (MCP), enabling prompt-assisted 3D modeling, scene creation, and manipulation.17MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Huxley-Brown/Project-Setup-MCP-Project'
If you have feedback or need assistance with the MCP directory API, please join our Discord server