MCP Gateway is a platform that connects AI assistants to internal tools such as databases and filesystems through a single authenticated endpoint, while enforcing role-based access control and logging all actions.
From the registry: Multi-tenant MCP platform with OAuth 2.1, Entra SSO, RBAC and audit logging.
Please install the `mcp-gateway` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Deploy MCP Gateway** — MCP Gateway is a self-hosted production platform that authenticates users, enforces RBAC, and exposes databases as MCP tools. Deploy via docker-compose or locally; then clients connect via mcp-remote bridge. (https://github.com/PanosSalt/MCP-Gateway)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","mcp-remote","http://localhost:8000/t/my-org/mcp/sse"]
Note: Self-hosted MCP Gateway — multi-tenant platform with OAuth 2.1+PKCE, RBAC, audit logs, SQL and filesystem tools. Clients use mcp-remote as stdio bridge to the SSE endpoint.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.SECRET_KEYrequiredJWT signing secret — use a random 64-char string.ENCRYPTION_KEYrequiredFernet AES key for DB credentials — minimum 32 characters.POSTGRES_PASSWORDrequiredPostgreSQL password used by docker-compose.ANTHROPIC_API_KEYrequiredRequired for the natural language query endpoint.AI-powered threat hunting and incident response MCP server for Elasticsearch/OpenSearch