1. Conduid
  2. Developer Tools
  3. Center
MCP server · Developer Tools

Center

A centralized platform for managing and connecting MCP servers. MCP Center provides a high-performance proxy service that enables seamless communication between MCP clients and multiple MCP servers.

Unclaimed Apache-2.0 last commit a year ago devtools
61Good

Scored 12 days ago · breakdown

About Center

Center is an MCP server published by noeio-net in the Developer Tools category: a centralized platform for managing and connecting MCP servers. MCP Center provides a high-performance proxy service that enables seamless communication between MCP clients and multiple MCP servers.

The repository has 40 stars and 10 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/noeio-net/mcp-center

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Center

Powered by Claude · Grounded in docs

I know everything about Center. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 5 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • ✓Tests presentA test suite exists in the repository.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

Releases

0.1.0Release 0.1.0 · 10 Sep 2025Docker Image docker pull nautilusops/mcp-center:0.1.0 Features MCP Server Registry: Centralized management of MCP server endpoints Reverse Proxy Service: High-performance proxy for MCP client-server communication Multiple Transport…

README

MCP Center

MacOS Rust MCP

A centralized platform for managing and connecting MCP (Model Context Protocol) servers. MCP Center provides a high-performance proxy service that enables seamless communication between MCP clients and multiple MCP servers.

Motivation

In our Kubernetes cluster, we have deployed various MCP Servers, including both in-house and third-party implementations, each running as independent services. Accessing these services currently requires configuring separate K8s Ingress or Service Gateway for each MCP Server, which increases operational complexity and maintenance overhead.

To address this, we propose a centralized MCP registry and reverse-proxy service that enables managed hosting of MCP Servers, which can be deployed either on Docker or Kubernetes. With this centralized service:

  • Service discovery becomes unified, eliminating the need to configure access paths for each MCP Server individually.
  • Authentication can be managed consistently across all MCP Servers, enhancing system security.
  • Leveraging a plugin system, we can modify or filter MCP Tool parameters, enabling tool-level traceability and monitoring (see issue #7).
  • Lifecycle management of MCP Servers can be standardized, simplifying deployment, scaling, and upgrades.

This approach improves maintainability, provides a foundation for future features such as unified tracing, auditing, and monitoring, and allows organizations to easily manage and host MCP Servers across different environments.

Architecture

architecture_diagram.png

Features

  • MCP SSE Transport Proxy - Server-Sent Events transport support
  • MCP Streamable Transport Proxy - Streamable transport protocol support
  • Multiple Registry Types - Support for memory-based and external API registries
  • High Performance - Built with Axum proxy framework for optimal performance
  • Kubernetes Ready - Complete Helm chart for easy deployment

Quick Start

Using Docker

# 1. Pull the latest image
docker pull nautilusops/mcp-center:latest

# 2. Start the container
docker run -d \
  --name mcp-center \
  -p 5432:5432 \
  -e MCP_ADMIN_TOKEN=your-custom-token \
  -e POSTGRES_HOST=your-postgres-host \
  -e POSTGRES_PORT=your-postgres-port \
  -e POSTGRES_USERNAME=your-postgres-username \
  -e POSTGRES_PASSWORD=your-postgres-password \
  -e POSTGRES_DATABASE=your-postgres-database \
  nautilusops/mcp-center:latest

Using Helm

Please see here to deploy with helm

From Source

# Clone the repository
git clone https://github.com/nautilus-ops/mcp-center.git
cd mcp-center

# Build the project
cargo build --release

# Set environments
export MCP_ADMIN_TOKEN=your-custom-token
export POSTGRES_HOST=your-postgres-host
export POSTGRES_PORT=your-postgres-port
export POSTGRES_USERNAME=your-postgres-username
export POSTGRES_PASSWORD=your-postgres-password
export POSTGRES_DATABASE=your-postgres-database

# Run the application
./target/release/mcp-center run --config bootstrap.toml

Usage Examples

1. Register MCP Server

curl -X POST http://localhost:5432/api/registry/mcp-server \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer your-admin-token" \
  -d '{
    "name": "my-mcp-server",
    "tag": "1.0.0",
    "endpoint": "http://my-server:8080/sse",
    "transport_type": "sse",
    "description": "My MCP server"
  }'

2. Get All MCP Servers

curl -X GET http://localhost:5432/api/registry/mcp-server \
  -H "Authorization: Bearer your-admin-token"

3. Connect to MCP Server via Proxy

curl -X GET http://localhost:5432/proxy/connect/my-mcp-server/1.0.0 \
  -H "Authorization: Bearer your-api-key"

Development

Prerequisites

  • Rust 1.89.0 or later
  • Docker (for containerized builds)
  • Kubernetes cluster (for deployment testing)

Building

# Development build
cargo build

# Release build
cargo build --release

# Docker build
docker build -t mcp-center .

Testing

# Run unit tests
cargo test

# Run integration tests
cargo test --test integration

# Run with specific features
cargo test --features integration

Contributing

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

This project is licensed under the Apache License, Version 2.0 - see the LICENSE file for details.

Roadmap

  • MCP Server Registry Center: Centralized management of MCP server endpoints
  • Authentication & Authorization: JWT-based authentication
  • Metrics & Monitoring: Prometheus metrics and Grafana dashboards
  • Load Balancing: Advanced load balancing algorithms
  • Rate Limiting: Request rate limiting and throttling
  • Plugin System: Extensible plugin architecture

README fetched from the repository 5 days ago. The original is authoritative.

Questions

About Center

How do I install Center?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Center safe to use with an AI agent?

Its trust score is 61 out of 100 (good). It passes 5 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Center still maintained?

The last commit was a year ago and 3 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.