MCP Servers Testing and Deployment

MCP Servers Build and Deployment Plan (Migrated from ACTION-PLANS, 2026-02-07)

Date: February 7, 2026 Status: Build Complete - Ready for Deployment Session: Continuation of Issue #392 (Drupal AI Agent Platform)

Executive Summary

Successfully built and tested 3 production-ready MCP servers with 32 MCP tools total:

OSSA Registry MCP Server (9 tools) - Agent discovery and validation
Drupal MCP Server (11 tools) - Drupal CMI, entities, and cache management
API Schema MCP Server (12 tools) - OpenAPI validation, generation, and linting

All servers compiled successfully, runtime tested, and ready for deployment.

1. OSSA Registry MCP Server

Location: agent-buildkit/packages/ossa-registry-mcp-server/ Package: @blueflyio/ossa-registry-mcp-server v1.0.0 Status: Build Successful + Runtime Verified

Dependencies: @modelcontextprotocol/sdk@^1.26.0, zod@^3.22.4, yaml@^2.3.4, glob@^10.3.10, chokidar@^3.5.3

9 MCP Tools:

Tool Name	Purpose
`list_agents`	Query all agents with filter/limit
`get_agent`	Get agent by ID
`search_agents`	Full-text search across fields
`get_agent_by_capability`	Capability-based search
`validate_manifest`	OSSA v0.4.1 validation
`validate_tools`	Tool definition validation
`validate_triggers`	Trigger validation
`get_agent_metrics`	Metrics and statistics
`get_health_score`	Agent health scoring

Services Architecture:

server.ts - MCP server main entry
services/registry-reader.service.ts - Filesystem-based registry reader
services/validation.service.ts - OSSA v0.4.1 validation
services/metrics.service.ts - Health scoring and metrics
tools/query.tools.ts - 4 query tools
tools/validation.tools.ts - 3 validation tools
tools/metrics.tools.ts - 2 metrics tools

2. Drupal MCP Server

Location: agent-buildkit/packages/drupal-mcp-server/ Package: @blueflyio/drupal-mcp-server v1.0.0 Status: Build Successful

11 MCP Tools:

Category	Tool Name	Purpose
Config Management	`drupal_get_config`	Get configuration by name
	`drupal_export_config`	Export config to YAML
	`drupal_import_config`	Import config from YAML
	`drupal_compare_config`	Compare environments
Entity CRUD	`drupal_create_entity`	Create Drupal entity
	`drupal_read_entity`	Read Drupal entity
	`drupal_update_entity`	Update Drupal entity
	`drupal_delete_entity`	Delete Drupal entity
	`drupal_query_entities`	Query entities with filters
Cache Management	`drupal_clear_cache`	Clear specific caches
	`drupal_rebuild_cache`	Rebuild cache system

Key Features: Full CMI integration, complete entity CRUD, granular cache control, Zod validation, DRY HTTP client.

3. API Schema MCP Server

Location: agent-buildkit/packages/api-schema-mcp-server/ Package: @blueflyio/api-schema-mcp-server v1.0.0 Status: Build Successful

12 MCP Tools:

Category	Tool Name	Purpose
Registry	`register_schema`	Register OpenAPI spec
	`list_schemas`	List all registered schemas
	`get_schema`	Get schema by ID
	`unregister_schema`	Remove schema
Validation	`validate_schema`	Validate OpenAPI 3.1 spec
	`validate_against_schema`	Validate data against schema
	`lint_schema`	Lint (recommended/strict/minimal)
	`check_breaking_changes`	Detect breaking API changes
Generation	`generate_types`	Generate TypeScript types
	`generate_validators`	Generate Zod validators
	`generate_docs`	Generate API documentation
	`generate_client`	Generate API client code

Build Fixes Applied (All Servers)

Updated MCP SDK from 0.5.0 to 1.26.0 (latest)
Fixed TypeScript configuration: added types: ["node"], changed module to commonjs
Installed @types/node in all packages
Fixed openapi-diff version from 0.27.0 to 0.24.1
Changed fast-glob to glob for consistency
Fixed Zod schema access: _def.schema to type assertions
Fixed TypeScript type assertions in API Schema MCP (response, schema, contact)

Build Results

Server	Build	Runtime	Dist Size
OSSA Registry	PASS	PASS	~15 KB
Drupal	PASS	Needs Drupal config	~18 KB
API Schema	PASS	Needs schema path	~25 KB

Deployment Plan

Phase 1: Local Testing (Week 1)

Claude Desktop configuration for each server with environment variables (REGISTRY_PATH, DRUPAL_BASE_URL, SCHEMA_REGISTRY_PATH).

Phase 2: Infrastructure Deployment (Week 2)

Target: Synology NAS (100.104.119.76)

Recommended: MCP Gateway approach (single entry point at port 4005):

mcp.blueflyagents.com:4005 - MCP Gateway
Individual ports: 4006 (OSSA), 4007 (Drupal), 4008 (API Schema)

Process management via PM2 with auto-restart, memory limits (500M), and monitoring.

Phase 3: Integration Testing (Week 3)

Claude Desktop integration: verify all 32 tools in tool palette
Agent integration: test with drupal-config-drift agent
Performance benchmarks: <100ms latency target, 10 concurrent requests, <500MB memory

Phase 4: Monitoring and Observability (Week 4)

Structured logging (Winston)
Prometheus metrics (tool invocations, duration histograms)
Health check endpoints (/health, /ready)

Architecture Integration

OSSA Ecosystem (openstandardagents)
        |
MCP Layer (3 servers, 32 tools)
        |
Agent Layer (drupal-config-drift + 6 planned agents)
        |
Infrastructure (Synology NAS, Cloudflare tunnels)

Issue #392 Progress

Completed: MCP Infrastructure (3 servers), first agent (drupal-config-drift, commit 89ea38ff)

Remaining: 6 more Drupal agents (accessibility, content-lifecycle, performance, incident-response, multisite-auditor, migration) + 2 enhanced agents (security-scanner + Drupal pack, ci-fixer-worker + Drupal CI/CD pack)

Lessons Learned

MCP SDK Version Matters - Always use latest stable (1.26.0)
TypeScript Module Resolution - CommonJS safer for Node.js servers
Zod Schema Access Changed - Use type assertions with v3
Package Version Validation - Always verify versions exist on npm
Fix Issues Incrementally - One server at a time, verify each fix