> ## Documentation Index > Fetch the complete documentation index at: https://docs.mcpmanager.ai/llms.txt > Use this file to discover all available pages before exploring further. # Features > A complete index of MCP Manager capabilities — gateways and server types, identity and OAuth, tool and feature provisioning, threat prevention, DLP filtering, platform security, observability, alerts, and team administration. **MCP Manager** puts one governed gateway between your AI clients and your MCP servers, giving you fine-grained control over how hosts, agents, and tools connect. This page is the full index of what MCP Manager does today — every distinct capability in one scannable list. Select any card to open the detailed documentation for that feature. Many features below are gated by a **capability** assigned to your role. If you don't see a page, tab, or button described here, your role likely lacks the relevant capability — ask a workspace administrator. See [Capabilities](/deployment/rbac-and-roles/capabilities). ## Deployment and enablement The gateway is the control point: one governed URL that every host and agent connects to, fronting all of your MCP servers. MCP Manager supports remote, managed, and workstation servers, unlimited gateways, and unlimited servers per gateway. One governed URL that aggregates many upstream MCP servers behind a single endpoint. Compatible with Anthropic, OpenAI, and all MCP-compatible environments. A guided, reuse-friendly authorization flow for Claude, Cursor, and other clients. Deploy Remote, Managed, and Workstation MCP servers. Connect any HTTPS MCP endpoint, whether a SaaS vendor's or your own self-hosted server. Launch a server in your infrastructure with a command MCP Manager generates. Run both command-based (stdio) and URL-based servers as managed endpoints. Reach servers on a local machine through an encrypted tunnel, never exposed to the internet. Group multiple managed or workstation servers into one logical unit. Spin up gateways for dev, staging, production, or per-team use. Scale without limits or concurrency concerns. Secure endpoints and access tokens are generated for you. MCP Manager learns and previews each server's live tools, prompts, resources, and templates. Run one org-wide gateway, one per team, one per server, or one per use case. Soft-delete and later restore gateways without losing their history. ## Identity and authentication MCP Manager brokers identity between hosts and servers so credentials never live in the client. An administrator chooses, per server, between each user's own identity and a shared service account. Every server uses secure, standards-based authentication. Automates identity onboarding for new servers (RFC 7591). Detects authorization endpoints from well-known metadata (RFC 8414 / RFC 9728). Automatically refreshes and rotates tokens to eliminate stale credentials. Choose a shared service account or per-user identity for each server on a gateway. Each user authenticates with their own downstream identity; no shared keys in clients. Pass the end user's identity to upstream servers so an agent acts as the real user. Issue each headless agent its own identity, scoped to a gateway connection. Validate caller JWTs and forward auth headers to upstream servers per request. Support servers that authenticate with custom headers or API keys. Broker enterprise single sign-on through Okta, Entra ID, and other IdPs. ## Tool and feature provisioning Decide exactly which tools, prompts, and resources each agent can reach. The allowlist mode is fail-closed by design — once you limit a feature type to selected capabilities, anything you haven't allowed is blocked. (A newly assigned server starts by allowing all of its capabilities, so a simple setup works without curation.) Allow-all, allow-selected, or block-all for tools, resources, and prompts per server. Tools, prompts, resources, and resource templates, uniformly. Limit the metadata agents receive to cut token usage, context overload, and cost. Pin a tool by name, title, or description so unreviewed changes stop passing the gateway. In allow-if-conditions-met mode, anything you haven't explicitly allowed is blocked. Prefix tool names to prevent collisions between servers on the same gateway. Different teams or users see different curated tool sets. Assign fine-grained provisioning control to specific roles. ## Threat prevention MCP Manager neutralizes the MCP-specific attack classes that put agents and data at risk, from prompt injection to rug pulls and server spoofing. Blocks malicious prompt content — including indirect, second-order injection in tool results. Detects and halts when a server or tool changes behavior after initial approval. Prevents modified or malicious tools from being served to agents. Stops attackers from creating look-alike servers that impersonate trusted ones. Authenticates each server connection using signed tokens and verifiable origins. Prevents one server from secretly invoking another server's tools without authorization. Instantly disable a host, connection, or identity when something looks wrong. Sensitive payload keys are scrubbed before logs and alerts are stored. ## Filtering and data loss prevention Gateway rules inspect MCP messages in flight and pass, modify, or block them, with five enforcement actions and a choice of detection methods. Detect and block sensitive patterns — phone numbers, SSNs, API keys, project IDs. Five enforcement actions on detected content: block, redact, replace, mask, and hash. Pre-trained PII detection and anonymization, run as a managed add-on. Connect internal DLP systems or third-party review workflows via custom rule engines. Managed prompt-injection, jailbreak, PII, and toxic-content detection. Apply Bedrock guardrails as a gateway rule engine. Detect and block jailbreak attempts via Lakera Guard and Bedrock Guardrails. Every rule engine returns an enforcement action the gateway applies inline. Choose whether a rule-engine outage allows or blocks traffic. Build a custom rule engine to block sensitive content or paths, such as a specific folder. ## Platform security and trust The gateway is hardened as the single control point in the path of every call, with encryption at rest and in transit, static egress IPs, and negligible added latency. All stored credentials are encrypted at rest with authenticated encryption. Encryption keys are rotated without operator intervention. Every connection is terminated and re-originated over TLS by design. Lock down upstream servers to MCP Manager's fixed egress IPs, with per-server shared secrets. Workstation servers stay private behind an encrypted tunnel, never exposed to the internet. The gateway adds roughly 150 ms or less, until inline rule engines run. ## Observability and reporting Every request and response is logged with rich context, attributed to the real user, and rolled up into charts and exports. View and manage all connected servers from one dashboard. See every host and agent connecting through your gateways, attributed to an identity. Logs full requests and responses alongside 20+ metadata fields per call. Every call is attributed to the real user behind it, supporting non-repudiation. Correlate a single request across client, gateway, and downstream server legs. Token counts are estimated per call. Token counts and feature calls grouped by user, team, and server. Token use, feature calls, server popularity, error rates, and latency percentiles. Median and 95th-percentile call duration per feature. Export audit data as CSV or JSON. Forward structured logs and request traces to any OpenTelemetry (OTLP) collector. Datadog, Grafana Cloud, Honeycomb, New Relic, and a self-hosted collector for any backend. ## Monitoring and alerts MCP Manager surfaces operational and security events as alerts so administrators stay aware of access requests, new tools, policy violations, and outages. Receive alerts when users request new gateway access. Get notified when new tools are added to your servers. Monitor sensitive data or policy violations in real time. Stay aware of broken connections or downtime instantly. Get notified when a server's OAuth callback or client registration fails. Per-origin and per-key rate limits protect the gateway from abuse. ## Administration, teams, and access control Provision people, scope access by team and capability, and integrate your identity provider for SSO and SCIM. Log in through your corporate identity provider. Automate user provisioning and de-provisioning (SCIM 2.0). Map Okta or Entra ID groups to MCP Manager teams, with just-in-time provisioning. Build custom roles from granular capabilities across every area of the product. Compose view-only roles — view reports, see alerts, view logs — for compliance reviewers. Define who can view or edit each gateway. Restrict visibility and data access within a workspace. Control what each team can deploy or modify. Register hosts, issue and revoke API tokens, and enable or disable connections. Funnel all MCP usage through the gateway with connector allowlists, MDM/EDR, and static IPs. Configure workspace name, date and time formats, and your plan. Invite users and revoke workspace access. For the security model behind these features — authentication, feature governance, runtime protections, and audit — see the [Security](/security/authentication-and-identity) section. ## Further reading What an end user experiences when connecting a gateway, step by step. Authentication, feature governance, runtime protections, and audit. Choose a gateway topology — org-wide, per team, per server, or per use case.