Manage MCP Servers
Configure and govern pre-built and custom MCP servers in the JFrog MCP Registry.
This section explains how administrators configure and govern pre-built MCP servers from the public registry and custom MCP servers from JFrog Artifactory. Both server types use JFrog Agent Guard, tool policies, and project scoping for every agent call.
Pre-built MCP Servers (Local and Remote)
The JFrog Agent Guard enforces a consistent set of policies across both local and remote MCPs, wrapping each server individually so every agent call is governed.
These are public, curated MCP servers indexed from the public MCP Registry. Your administrators can browse the catalog, review the available servers, and allow them for their projects.
The following table compares local and remote pre-built MCP servers.
| Aspect | Local Pre-built MCP servers | Remote Pre-built MCP servers |
|---|---|---|
| Definition | Executable packages (npm, Python) run on the developer machine. | URL endpoints (HTTP or SSE) that the agent connects to. |
| Resolution | Fetched and cached from JFrog Artifactory via the Agent Guard. | Referenced by URL; Agent Guard still enforces which remote servers are allowed. |
| Governance | Same tool policies and project scoping; binaries are scanned and versioned in JFrog Artifactory. | Same tool policies and project scoping; only approved remote URLs are routable. |
For more information, see Configure Pre-built MCP Servers.
Custom MCP Servers
These are private MCP servers registered from your organization's JFrog Artifactory repositories. They follow the same governance model but require validation before registration.
For more information, see Custom MCP Servers.
Governance Workflow
MCP Tool Policies provide granular control:
- Define which specific tools within an MCP server users can invoke.
- Use allow lists and deny lists with static text or regex patterns.
- Choose between "allow all tools" or "select tools manually" for each server.
- Override tool availability without unregistering the entire MCP server.
- Admins can restrict (remove) any MCP server at any time, immediately revoking developer access.
Related Topics
Updated 18 days ago