"A comparison for backend service architecture" matching MCP servers:

Manage a fleet of OPNsense firewalls from an AI agent, inside guardrails it can't drive around. MCP server for central management of OPNsense firewall fleets. 129 tools across devices, config sync, tasks, schedules, templates, backups and remote consoles - destructive actions confirmation-gated, MCP-issued tokens lifetime-bounded, backup and storage secrets excluded from the toolset entirely.

Connect to your TTRPG campaign's repository and database. Instead of retrieving prose, its 48 tools (20 read, 28 write) return typed state: 14 entity schemas (NPCs, factions, locations, sessions, lore), relationship and knowledge-graph queries, wiki blocks, and a narrative-state bundle of open threads and canon facts.

Enables LLMs to interact with embedded devices by reading and writing Segger RTT data through a J-Link debugger.

MCP server that integrates with VictoriaMetrics vmanomaly API to enable AI-assisted anomaly detection, model management, and configuration generation.

Enables AI assistants to explore a PostgreSQL database, run bounded read-only SQL, inspect query plans, test hypothetical indexes, find slow queries, and check database health with compact CSV output.

Open source MCP server specializing in easy, fast, and secure tools for Databases.

A local AST and type-aware Go repository context indexer that uses CHA to map symbols, call graphs, dependencies, and architecture patterns. Built for AI coding agents that need to navigate and reason about large Go codebases without reading raw files.

Local ledger for development ports: leases a block of ports per project slot (one per working copy), renders env files, and resolves service names to URLs. No daemon, no listener.

MCP server for gavel, a code-quality gate for Bazel monorepos. Exposes judge, findings, coverage and architecture tools so a coding agent can check its change against the quality gate (lint, coverage, layer rules) before declaring it done — all off the Bazel build graph, over just what changed.

Official MCP server for the Nhost backend platform. Manage Postgres data, GraphQL, auth, storage, migrations and Hasura metadata via AI assistants.

A high-performance Go-based MCP server that provides a microservice architecture for orchestrating diverse tools through gRPC and HTTP/REST APIs. Enables seamless integration of language-agnostic tools including ML capabilities, web search, calculations, and human interaction for intelligent agent workflows.

Self-hosted OpenTelemetry backend in one Go binary. Its MCP server exposes tools for service health, latency, topology, trace inspection, log search, read-only SQL over traces, logs and metrics, and dashboards.

A command-line interface and MCP server for managing and monitoring multiple development services through a unified terminal UI. It enables users to interact with service logs, filter messages, and control development environments directly via Model Context Protocol integration.

Enables AI assistants to interact with MAAS (Metal as a Service) infrastructure for machine management, network configuration, and storage management through a standardized JSON-RPC 2.0 interface.

Authenticated email service MCP for AI agents.

mcp-resile is a resilience gateway for the Model Context Protocol that sits in front of your own MCP servers and protects them from autonomous-agent traffic, with zero backend code changes.

Enables coding agents to debug backend requests by providing tools to list, view, wait for, diagnose, and clear request traces.

Enables administering Ubuntu hosts through MCP over stdio, currently exposing a read-only get_system_info tool that reports OS release, hostname, kernel, architecture, memory, and root filesystem capacity.

You are capable of interpreting golang code and judge it under the most strict ddd and clean architecture paragidms

Provides comprehensive access to the New Relic observability platform through 55 MCP tools, enabling APM, infrastructure, logs, traces, alerts, dashboards, synthetics, workflows, notifications, service levels, tags, entities, and workloads via a single GraphQL endpoint.