Enterprise MCP Gateway and Tool Registry
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Enterprise MCP Gateway and Tool Registrylist available tools"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Enterprise MCP Gateway and AI Tool Registry
Secure tool-discovery and execution gateway for AI-agent integrations. The project combines a runnable FastAPI gateway with an optional standards-based MCP server entrypoint built with the official Python MCP SDK.
Highlights
JWT authentication with demo admin, developer, and viewer roles
RBAC enforcement for tool execution and administrative operations
Persistent tool registry and audit logs with SQLAlchemy
Built-in calculator, summarizer, keyword extractor, and gateway-health tools
Allowlisted HTTP tool registration for controlled external API integration
Redis-backed rate limiting with an in-memory fallback
Optional OpenTelemetry export to Jaeger
Prometheus-style gateway metrics at
/metricsREST endpoints for browser testing and an optional FastMCP Streamable HTTP server
Automated tests and GitHub Actions CI
Related MCP server: mcp-tool-gateway
Architecture
AI Client / Developer
|
v
FastAPI Gateway -----> JWT Auth + RBAC
|
+-----> Tool Registry -----> Built-in Tools
| `----> Allowlisted HTTP Tools
|
+-----> Rate Limiter ------> Redis or in-memory fallback
|
+-----> Audit Store -------> SQLite quick start / PostgreSQL Docker mode
|
`-----> OpenTelemetry -----> Jaeger (optional)Quick Start
python -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements-dev.txt
cp .env.example .env
python -m uvicorn app.main:app --host 0.0.0.0 --port 8000Open http://localhost:8000/docs.
Demo Accounts
Username | Password | Role |
|
| admin |
|
| developer |
|
| viewer |
These are intentionally demo-only credentials. Replace the identity layer before deployment.
Run Tests
python -m pytest -qOptional Standards-Based MCP Server
python -m pip install -r requirements-mcp.txt
python mcp_server.pyConnect an MCP client or MCP Inspector to http://localhost:8000/mcp.
Docker Compose
docker compose up --buildAPI docs:
http://localhost:8000/docsJaeger UI:
http://localhost:16686
Documentation
See docs/ for setup, architecture, API reference, MCP notes, and security considerations.
Security Note
The REST gateway demonstrates authentication, authorization, rate limiting, auditing, and allowlisted outbound calls. The optional local MCP server is a separate SDK demonstration. A remote MCP deployment should use OAuth 2.1 resource-server protection and production identity infrastructure.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.62MIT
- AlicenseNot gradedqualityCmaintenanceA secure tool-execution plane for agentic AI that enforces JWT authentication, rate limiting, prompt-injection inspection, and audit logging, while ingesting downstream OpenAPI endpoints as MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to securely discover, execute, and observe tools with role-based access control and audit logging. Serves tools over MCP stdio and HTTP for integration with Claude Desktop, Cursor, and other clients.1
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Devarinti9/Enterprise-MCP-gateway-tool-registry'
If you have feedback or need assistance with the MCP directory API, please join our Discord server