mcp-server-enterprise-tools

mcp-server-enterprise-tools

MCP server for regulated enterprises, providing per-tool RBAC, redacted audit logging, and structured error handling. Exposes bank tools for customer lookup, statement search, and dispute resolution over stdio and HTTPS transports.

Category
Visit Server

README

mcp-server-enterprise-tools

Reference MCP server for regulated enterprises. Per-tool RBAC, redacted audit log, structured error envelope, and drop-in configs for Claude Desktop plus a plain HTTPS transport for internal agents.

Deployed URL: https://mcp-tools.internal.example (placeholder, replace in your fork; the terraform in terraform/ provisions an internal ALB you front with your own DNS).

The problem

MCP (Model Context Protocol, announced by Anthropic on 2024-11-25) standardizes how an LLM host discovers and calls tools. That is great for consumer laptops. For a bank it is not enough on its own:

  • MCP has no first-class caller identity, and a regulator needs to know who called what
  • tool arguments and results can carry PII (SSNs, PANs, account numbers), and those cannot land in cleartext in logs or audit tables
  • error handling in the spec is thin; internal callers need something machine-readable to branch on

This repo is an opinionated take on filling those gaps while keeping the tool implementations small and readable.

What is exposed

Three bank tools:

Tool Verb Purpose
customer_360.lookup read profile, primary account summary, risk flags
statement_search.query read full-text with date and amount filters
dispute_resolution.open mutating open a dispute against a transaction
dispute_resolution.status read dispute state by id

Each is a real MCP tool with a JSON input schema. Adding a fourth is a single file under src/mcp_server/tools/ plus a line in app.build_registry.

Architecture

              +--------------------+          +------------------+
              |  Claude Desktop    |          |  Internal agent  |
              |  (stdio)           |          |  (http)          |
              +---------+----------+          +---------+--------+
                        |                               |
                        |               X-Bank-Identity |
                        v                               v
                    +---+-------------------------------+---+
                    |          MCP server (this repo)        |
                    |  transport -> registry.call -> handler |
                    |                    |                   |
                    |            rbac.check + audit.write    |
                    +----+-----------------+----------+------+
                         |                 |          |
                         v                 v          v
                +------------------+  +---------+  +------------------+
                | bank internal    |  | Postgres|  | Prometheus       |
                | APIs (customer,  |  | audit   |  | metrics scraped  |
                | statements,      |  | log     |  | at /metrics      |
                | disputes)        |  +---------+  +------------------+
                +------------------+

Longer version with request flow: docs/architecture.md.

Quick start

Local (stdio, what Claude Desktop uses):

uv pip install -e '.[dev]'         # or plain pip
export AUDIT_DB_URL=sqlite:///./audit.db
export MCP_IDENTITY=user:local
make run

Local (http + postgres via compose):

docker compose up --build
# server on :8080, prometheus on :9090, postgres on :5432
curl -s -X POST http://localhost:8080/mcp/call \
  -H "X-Bank-Identity: svc-analyst-01" \
  -H "Content-Type: application/json" \
  -d '{"tool":"customer_360.lookup","args":{"customer_id":"C-01234567"}}'

Point Claude Desktop at the server: copy examples/claude_desktop_config.json into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the Windows equivalent. Walkthrough in docs/claude_desktop_setup.md.

RBAC model

Deny by default. Policies in configs/rbac.yaml map identities to allowed tool names, with a trailing .* wildcard for grouping. Every call, allowed or denied, writes an audit row. Full spec in docs/rbac_model.md.

Audit log design

One row per tool call, in Postgres. Columns: request_id, identity, tool, outcome, args_redacted, error_code, duration_ms, created_at.

Every string in args is passed through Redactor before persistence: SSNs, PANs (Luhn-checked), email addresses, and long numeric IDs are replaced with marked tokens. The upstream response is also sanitized before it leaves the process. Details in src/mcp_server/redaction.py and the tests.

Structured errors

Every failure comes back as an ErrorEnvelope:

{
  "error": {
    "code": "forbidden",
    "message": "identity 'svc-analyst-01' is not permitted to call 'dispute_resolution.open'",
    "request_id": "0d3f4a...",
    "tool": "dispute_resolution.open",
    "retryable": false,
    "details": {}
  }
}

Codes: unauthenticated, forbidden, not_found, invalid_argument, upstream_unavailable, rate_limited, internal. Clients can branch on code without string-matching messages.

Deploy

Terraform under terraform/ provisions an internal ALB, ECS Fargate service, and RDS Postgres for the audit log. make tf-plan to review.

Prod checklist:

  1. Populate a real configs/rbac.yaml. Prefer many narrow identities over a few broad ones.
  2. Wire the X-Bank-Identity header to be set by a trusted upstream (mTLS terminator, OIDC proxy). The server does not authenticate; it only reads the resolved identity.
  3. Ship the audit table to your SIEM nightly. The table is the source of truth.
  4. Rotate the break-glass credential weekly and alert on every use.

Repo layout

src/
  mcp_server/       server, registry, rbac, audit, redaction, tools/
  mcp_client/       stdio + http client used for testing and examples
configs/            default.yaml, rbac.yaml, prometheus.yml
terraform/          aws vpc + ecs + rds
tests/              rbac, audit, redaction, tools, registry
examples/           claude_desktop_config.json, transcripts
docs/               mcp primer, architecture, rbac model, claude setup

Status

Early. MCP shipped two weeks ago; the SDK will move. Pinned versions in pyproject.toml reflect what shipped with the announcement. Bump as the SDK stabilizes.

License

MIT. See LICENSE.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured