bank-api

The Bank API MCP server exposes a compliant Model Context Protocol (MCP) endpoint that mirrors the Bank API design reference. It serves as an MCP gateway to the underlying ASP.NET Core minimal API, providing standardized exposure of resources, authentication, and OpenAPI documentation via MCP tooling. Use the MCP endpoint to discover, describe, and interact with the bank resources using the MCP protocol semantics, including service discovery, contract validation, and downstream API calls. The server is designed to work with MCP clients and tooling that rely on the protocol for inter-service communication, and it leverages the project’s existing API surface (OpenAPI, JWS/JWK validation, and token-based security) to ensure secure, verifiable interactions. When you run the server, you can expect to access an MCP-safe entry point that coordinates with downstream endpoints, returning structured MCP responses for queries like account lookups, transactions, and balances, all while honoring the API’s security and compliance posture.

Prerequisites:

• Docker installed and running on your machine
• internet access to pull the MCP docker image

Installation steps:

1. Pull and run the MCP docker image (the command below starts the MCP server container in interactive mode):

docker run -i erwinkramer/bank-api-mcp:latest

2. If you need to customize, you can pass environment variables or mount configurations as needed. Example (override log level and server name):

docker run -i \
  -e MCP_SERVER_NAME=erwinkramer-bank-api \
  -e MCP_LOG_LEVEL=debug \
  erwinkramer/bank-api-mcp:latest

3. Verify the server is reachable by hitting the MCP well-known endpoint or the health check endpoint exposed by the container. Typical URLs may include the MCP discovery path and a health status path as documented by the container's entrypoint.

Prereqs recap:

• Docker installed and running
• Appropriate network access to pull images
• Optional: environment-specific configuration (server name, log level, credentials) via environment variables

Tips and notes:

• The MCP server is designed to expose a standard set of MCP endpoints aligned with the Bank API reference; use MCP tooling to discover and describe resources before invoking operations.
• If you encounter authentication or token validation issues, verify the OpenID Connect/JWK configuration that the Bank API uses, as the MCP server will validate signatures against those endpoints.
• For local testing, you can enable debug logging by setting MCP_LOG_LEVEL=debug in the container environment.
• Ensure network routing between the MCP container and any downstream services (or mock services) is allowed, especially if the container needs to call external APIs.
• If you publish or share the MCP endpoint, consider rotating credentials and limiting access to trusted clients per your security posture.