Skip to main content
Glama
Enhanced Architecture MCP

Enhanced Architecture MCP

Enhanced Architecture MCP

Enhanced Model Context Protocol (MCP) servers with professional accuracy, tool safety, user preferences, and intelligent context monitoring.

Overview

This repository contains a collection of MCP servers that provide advanced architecture capabilities for AI assistants, including:

  • Professional Accuracy Enforcement - Prevents marketing language and ensures factual descriptions

  • Tool Safety Protocols - Blocks prohibited operations and validates parameters

  • User Preference Management - Stores and applies communication and aesthetic preferences

  • Intelligent Context Monitoring - Automatic token estimation and threshold warnings

  • Multi-MCP Orchestration - Coordinated workflows across multiple servers

Related MCP server: Role-Specific Context MCP Server

Active Servers

Enhanced Architecture Server (enhanced_architecture_server_context.js)

Primary server with complete feature set:

  • Professional accuracy verification

  • Tool safety enforcement

  • User preference storage/retrieval

  • Context token tracking

  • Pattern storage and learning

  • Violation logging and metrics

Chain of Thought Server (cot_server.js)

Reasoning strand management:

  • Create and manage reasoning threads

  • Branch reasoning paths

  • Complete strands with conclusions

  • Cross-reference reasoning history

Local AI Server (local-ai-server.js)

Local model integration via Ollama:

  • Delegate heavy reasoning tasks

  • Token-efficient processing

  • Hybrid local+cloud analysis

  • Model capability queries

Installation

  1. Prerequisites:

    npm install
  2. Configuration: Update your Claude Desktop configuration to include the servers:

    {
      "mcpServers": {
        "enhanced-architecture": {
          "command": "node",
          "args": ["D:\\arch_mcp\\enhanced_architecture_server_context.js"],
          "env": {}
        },
        "cot-server": {
          "command": "node", 
          "args": ["D:\\arch_mcp\\cot_server.js"],
          "env": {}
        },
        "local-ai-server": {
          "command": "node",
          "args": ["D:\\arch_mcp\\local-ai-server.js"],
          "env": {}
        }
      }
    }
  3. Local AI Setup (Optional): Install Ollama and pull models:

    ollama pull llama3.1:8b

Usage

Professional Accuracy

Automatically prevents:

  • Marketing language ("revolutionary", "cutting-edge")

  • Competitor references

  • Technical specification enhancement

  • Promotional tone

Context Monitoring

Tracks conversation tokens across:

  • Document attachments

  • Artifacts and code

  • Tool calls and responses

  • System overhead

Provides warnings at 80% and 90% capacity limits.

User Preferences

Stores preferences for:

  • Communication style (brief professional)

  • Aesthetic approach (minimal)

  • Message format requirements

  • Tool usage patterns

Multi-MCP Workflows

Coordinates complex tasks:

  1. Create CoT reasoning strand

  2. Delegate analysis to local AI

  3. Store insights in memory

  4. Update architecture patterns

Key Features

  • Version-Free Operation - No version dependencies, capability-based reporting

  • Empirical Validation - 60+ validation gates for decision-making

  • Token Efficiency - Intelligent context management and compression

  • Professional Standards - Enterprise-grade accuracy and compliance

  • Cross-Session Learning - Persistent pattern storage and preference evolution

File Structure

D:\arch_mcp\
├── enhanced_architecture_server_context.js  # Main server
├── cot_server.js                            # Reasoning management
├── local-ai-server.js                       # Local AI integration
├── data/                                    # Runtime data (gitignored)
├── backup/                                  # Legacy server versions
└── package.json                             # Node.js dependencies

Development

Architecture Principles

  • Dual-System Enforcement - MCP tools + text document protocols

  • Empirical Grounding - Measurable validation over assumptions

  • User-Centric Design - Preference-driven behavior adaptation

  • Professional Standards - Enterprise accuracy and safety requirements

Adding New Features

  1. Update server tool definitions

  2. Implement handler functions

  3. Add empirical validation gates

  4. Update user preference options

  5. Test cross-MCP coordination

Troubleshooting

Server Connection Issues:

  • Check Node.js version compatibility

  • Verify file paths in configuration

  • Review server logs for syntax errors

Context Tracking:

  • Monitor token estimation accuracy

  • Adjust limits for conversation length

  • Use reset tools for fresh sessions

Performance:

  • Local AI requires Ollama installation

  • Context monitoring adds ~50ms overhead

  • Pattern storage optimized for < 2ms response

License

MIT License - see individual files for specific licensing terms.

Contributing

Architecture improvements welcome. Focus areas:

  • Enhanced token estimation accuracy

  • Additional validation gates

  • Cross-domain pattern recognition

  • Performance optimization

Available Tools

5 tools
hybrid_analysisC

Hybrid local+cloud analysis for complex data

Inputs: data (required), approach, model.

model_listB

List available local AI models

Inputs: no named parameters.

query_local_aiC

Query local AI model via Ollama for reasoning assistance

Inputs: prompt (required), model, temperature.

reasoning_assistC

Structured reasoning assistance for complex problems

Inputs: problem (required), steps, model.

token_efficient_reasoningB

Delegate heavy reasoning to local AI to conserve cloud tokens

Inputs: reasoning_task (required), context, model.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 5 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes that could cause confusion. 'query_local_ai' and 'reasoning_assist' both involve reasoning assistance with local AI, while 'hybrid_analysis' and 'token_efficient_reasoning' both address complex problem-solving with efficiency considerations. The descriptions don't clearly differentiate when to use one over the other.

    Naming Consistency3/5

    The naming conventions are mixed but still readable. 'model_list' and 'query_local_ai' follow a verb_noun pattern, while 'hybrid_analysis', 'reasoning_assist', and 'token_efficient_reasoning' use descriptive phrases without clear verbs. This inconsistency makes the set less predictable but not chaotic.

    Tool Count4/5

    With 5 tools, the count is reasonable for a server focused on AI and analysis tasks. It's slightly lean but covers core functionalities like listing models, querying AI, and analysis. A few more tools might enhance coverage, but this is within an appropriate range.

    Completeness3/5

    The toolset covers basic AI interaction and analysis but has notable gaps. There's no tool for managing or configuring models (e.g., load/unload), updating analysis parameters, or handling errors. The domain suggests more lifecycle operations, but agents can work around this with the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers