Stevennevins Architect MCP Server

🚀 MCP Server Template

This MCP Server Template offers a seamless way to develop and test applications that interact with large language models (LLMs). It provides a structured environment with tools for development, testing, and debugging.

🚀 Quick Start

Prerequisites

LLM CLI Installation

This project requires the installation of the Large Language Model (LLM) Command Line Interface (CLI). You can install it using Homebrew:

brew install llm

After installation, ensure that the llm command is available in your PATH. Run the following command to verify:

llm --version

Development

1. Install dependencies:

npm install

2. Start the development server with hot reloading:

npm run dev

3. Build the project:

npm run build

4. Run tests:

npm test

5. Start the production server:

npm start

✨ Features

Architecture Tool

The architecture tool in src/tools/architect.ts provides an interface to interact with the LLM CLI for obtaining architectural design feedback. It maintains the conversation context and handles communication between the application and the LLM CLI.

• Maintain conversation context across multiple interactions.
• Handle command execution via the LLM CLI.
• Provide error handling and logging.
• Support both new conversation and continued discussion modes.

Requirements

• The LLM CLI must be installed and configured (see the Prerequisites section).
• Environment variables should be correctly configured to support the LLM CLI.

📦 Installation

Using TestClient

The template includes a built - in TestClient for local testing and an MCP inspector for visual debugging.

import { TestClient } from "./utils/TestClient";

describe("YourTool", () => {
  const client = new TestClient();

  it("should process data correctly", async () => {
    await client.assertToolCall(
      "your-tool-name",
      { input: "test" },
      (result) => {
        expect(result.toolResult.content).toBeDefined();
      }
    );
  });
});

Using MCP Inspector

The template includes an MCP inspector for visual debugging of tools:

1. Start the inspector:

npx @modelcontextprotocol/inspector node dist/index.js

2. Open the inspector interface in your browser: http://localhost:5173

Using Cursor for Local Testing

To test your MCP server locally in Cursor:

1. Build and link the package:

npm run build
npm run link

2. Verify that the binary works correctly:

npx architect-test-mcp-tool

3. Add the server to Cursor:
   • Open Cursor settings.
   • Click on the "Features" tab.
   • Scroll to the bottom and find the "MCP Server" section.
   • Click "Add Server".
   • Select the "Command" type.
   • Enter a name (e.g., "Local Example Tool").
   • Enter the command: npx architect-test-mcp-tool.
   • Click "Confirm".
4. Check the MCP Server section in Cursor to ensure your server is running.

⚠️ Important Note

If you make changes to the code, remember to rebuild and relink:

npm run build
npm run link

After testing, you can unlink using the following command:

npm run unlink

This command deletes the global symbolic link created during development.

🔧 Technical Details

Inspector Features

• Maintain conversation context: Ensure that the tool maintains a consistent context across multiple interactions.
• Handle LLM commands: Execute large language model - related operations via the CLI.
• Error handling and logging: Provide detailed error information and logs to assist with debugging.

Dependency Management

Use the Node Package Manager (npm) for dependency installation and version management to ensure the smooth running of the project.