Get the FREE Ultimate OpenClaw Setup Guide →

architect

MCP server from stevennevins/architect-mcp-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio stevennevins-architect-mcp-server node dist/index.js \
  --env LLM_CLI_PATH="path/to/llm (ensure llm is installed and available in PATH)"

How to use

This MCP server exposes the Architect tool, which provides an interface to leverage the LLM CLI for architectural design feedback. It maintains conversation context across interactions, handles command execution through the LLM CLI, and includes error handling and logging to help you iterate on designs with continuity. You can start the server in production mode after building, and use the provided tooling to test and inspect tool calls.

Once running, you can issue architectural prompts to the Architect tool to receive structured design guidance, feasibility analysis, and iterative refinements. The built-in testing utilities and the MCP Inspector help you validate tool schemas, monitor request/response payloads, and debug interactions between your server and clients. For local testing, you can use the included TestClient to simulate tool calls and verify results before integrating into your application.

How to install

Prerequisites:

  • Node.js (recommended LTS) and npm installed
  • LLM CLI installed and available in your PATH (per Prerequisites)

Installation steps:

  1. Install dependencies
npm install
  1. Run development server (hot reload during development)
npm run dev
  1. Build the project for production
npm run build
  1. Run tests
npm test
  1. Start the production server
npm start

Note: If you modify code and want to test changes locally, rebuild and relink as needed. The README mentions using Cursor for local testing and the MCP Inspector for debugging; you can follow those workflows to validate your setup.

Additional notes

Tips and common issues:

  • Ensure the LLM CLI is properly installed and accessible in your PATH before starting the server.
  • If you encounter context loss in conversations, verify any state persistence mechanisms in your deployment environment.
  • Use the MCP Inspector to view tool schemas and test calls interactively, which helps diagnose schema mismatches or payload issues.
  • When testing locally, remember to build before running the inspector or TestClient to ensure you're testing against the latest code.
  • If you change environment-related settings, restart the server to apply changes.

Related MCP Servers

Sponsor this space

Reach thousands of developers