Eunomia MCP Server

what is Eunomia MCP Server about?

Enables the application of Eunomia instruments (e.g., PII detection, IDBac) to text streams processed by MCP‑based servers, ensuring automatic enforcement of privacy and access policies.

how to use Eunomia MCP Server?

1. Clone the repository.
2. Define application settings using a Pydantic BaseSettings class, specifying MCP_SERVERS and an Orchestra with desired instruments.
3. Launch the server with uv --directory "path/to/server/" run orchestra_server (or equivalent command).
4. The server loads settings from environment variables or a .env file, starts the configured MCP server(s), and applies the defined instruments to incoming text.

key features of Eunomia MCP Server

• Seamless integration of Eunomia instruments with any MCP‑compatible server.
• Simple declarative configuration via Pydantic Settings.
• Support for multiple MCP servers orchestrated in parallel.
• Built‑in privacy instruments like PiiInstrument with replace edit mode.
• Extensible to add custom instruments (e.g., IdbacInstrument).

use cases of Eunomia MCP Server

• Enforcing PII redaction in chatbot or LLM applications.
• Applying compliance checks (e.g., GDPR) before data reaches downstream services.
• Coordinating multiple micro‑services that communicate over MCP while maintaining consistent data governance.
• Rapid prototyping of privacy‑aware pipelines for internal tools.

FAQ from the Eunomia MCP Server

• Is this project still actively maintained? The repository displays a deprecation warning; a new MCP integration is under development.
• Can I use it with other MCP servers besides the web‑browser example? Yes, any MCP‑compatible server can be added to the MCP_SERVERS configuration.
• Do I need to install additional dependencies? Apart from the repository code, you need uv (or an equivalent Python task runner) and the target MCP server packages.
• How are environment variables passed to the MCP servers? They are specified under the env key of each server entry in the settings.
• Can I customize the instrument behavior? Instruments expose parameters such as entities and edit_mode which can be set when constructing them in the Orchestra.

[!WARNING] This MCP server is deprecated as it is not compatible with the latest developments of Eunomia. A new MCP integration is under development and will be available soon.

Eunomia MCP Server

Open Source Data Governance for LLM-based Applications — with MCP integration

Made with ❤ by the team at What About You.

Read the docs · Join the Discord

Overview

Eunomia MCP Server is an extension of the Eunomia framework that connects Eunomia instruments with MCP servers. It provides a simple way to orchestrate data governance policies (like PII detection or user access control) and seamlessly integrate them with external server processes in the MCP ecosystem.

With Eunomia MCP Server, you can:

• Enforce data governance on top of LLM or other text-based pipelines.
• Orchestrate multiple servers that communicate via the MCP framework.

Get Started

Installation

git clone https://github.com/whataboutyou-ai/eunomia-mcp-server.git

Basic Usage

Eunomia MCP Server uses the same "instrument" concept as Eunomia. By defining your set of instruments in an Orchestra, you can apply data governance policies to text streams that flow through your MCP-based servers.

Below is a simplified example of how to define application settings and run the MCP server with uv.

"""
Example Settings for MCP Orchestra Server
=========================================
This example shows how we can combine Eunomia with a web-browser-mcp-server
(https://github.com/blazickjp/web-browser-mcp-server).
"""

from pydantic_settings import BaseSettings
from pydantic import ConfigDict
from eunomia.orchestra import Orchestra
from eunomia.instruments import IdbacInstrument, PiiInstrument


class Settings(BaseSettings):
    """
    Application settings class for MCP orchestra server using pydantic_settings.

    Attributes:
        APP_NAME (str): Name of the application
        APP_VERSION (str): Current version of the application
        LOG_LEVEL (str): Logging level (default: "info")
        MCP_SERVERS (dict): Servers to be connected
        ORCHESTRA (Orchestra): Orchestra class from Eunomia to define data governance policies
    """

    APP_NAME: str = "mcp-server_orchestra"
    APP_VERSION: str = "0.1.0"
    LOG_LEVEL: str = "info"
    MCP_SERVERS: dict = {
        "web-browser-mcp-server": {
            "command": "uv",
            "args": [
                "tool",
                "run",
                "web-browser-mcp-server"
            ],
            "env": {
                "REQUEST_TIMEOUT": "30"
            }
        }
    }
    ORCHESTRA: Orchestra = Orchestra(
        instruments=[
            PiiInstrument(entities=["EMAIL_ADDRESS", "PERSON"], edit_mode="replace"),
            # You can add more instruments here
            # e.g., IdbacInstrument(), etc.
        ]
    )

Running the Server

Once your settings are defined, you can run the MCP Orchestra server by pointing uv to the directory containing your server code, for example:

uv --directory "path/to/server/" run orchestra_server

This will:

1. Load the settings from .env or environment variables.
2. Launch the Eunomia MCP Server to handle requests and orchestrate your external MCP server(s).
3. Apply Eunomia instruments (like PiiInstrument) to the incoming text, ensuring data governance policies are automatically enforced.

Further Reading

For more detailed usage, advanced configuration, and additional instruments, check out the following resources:

• Eunomia Documentation: Learn more about the core Eunomia framework.
• Eunomia Repository: See Eunomia source code and examples.
• MCP Documentation: Explore the Model Context Protocol specification and ecosystem.