Troubleshooting

Common FAQs and Troubleshooting for the JFrog MCP Registry

General MCP Registry Issues

  • Unexpected tools allowed? Review your Regex patterns. A broad pattern might be matching more tools than you intended.

  • MCP failed to start? The Gateway does not install runtimes. Ensure you have Docker, Python, or Node installed locally, or make sure the correct environment variables are configured.

  • Tools are not appearing in my agent chat. Permissions are Project-Specific. Ensure you allowed the MCP for the specific project configured in your CLI (and that your Regex patterns aren't inadvertently blocking the tools).

  • mcp-gateway command is not recognized: In order to use the MCP Gateway CLI commands, you must first install the mcp gateway.

  • How to ensure the agent provides the required info: Make sure your prompt is accurate and clear, so that the agent understands that you are looking for specific MCPs or Tools from the JFrog MCP Gateway.

  • Why does the tool list say "AI-Generated"? We run the MCP through an AI analysis to predict the tools it exposes. This helps you set up policies before you even download the tool, but be aware that it is a discovered suggestion list, not a hard-coded manifest.

  • How do I configure API keys for an MCP? Some MCPs require environment variables (like API keys) to function. You can pre-populate these in the Config tab of the MCP details page, or define them locally when adding MCP servers.

  • How do I check if an MCP is safe to use? Before adding an MCP to your allowed list, click the server card in the Discovery tab. Review the Licenses tab and malicious status to ensure the tool meets your organization's compliance standards.

  • How do I allow an MCP server for my team? See Allow MCP Servers.

  • How do I block dangerous commands (for example, "delete"), while allowing others? See Configure Tool Policies for creating Allow and Deny lists.

  • How do I uninstall the JFrog MCP Gateway?

    1. Run this command in the terminal, it will remove the plugin and remove the dependend files:

      jf plugin ui mcp-gateway
      rm -rf ~/.jfrog/jfrogmcp.json ~/.jfrog/jfrogmcp.conf.json
      rm -rf ~/.jfrog/.env
    2. Remove the MCP Server from the MCP list in the IDE. For example, in Cursor:

  • How do I configure runtime arguments for a server?

    You configure runtime arguments for a server during the process of adding it to the registry.

    Here is how you can do it based on the sources:

    1. When adding a server to the registry, proceed to Step 2: Configuration in the "Add to Registry" wizard. In this step, you will see a section for "Required configuration" which allows you to set both environment variables and runtime arguments.
    2. Click on the Runtime arguments tab (located right next to the Environment variables tab) to enter your configuration.
    3. After you have saved your configuration and the server is successfully added to a project, you can view the configured runtime arguments at any time by navigating to the Configuration tab on the MCP Server Details page.
  • How do I set environment variables as secrets?

    1. During Step 2 (Configuration) of the "Add to Registry" wizard, navigate to the Environment variables tab.
    2. Next to the specific environment variable you are configuring, click the toggle switch labeled Secret to turn it on.

Troubleshooting Custom MCPs

The following table describes common errors that can occur during registration or unregistration of custom MCPs.

ErrorCauseResolution
MISSING_MANDATORY_FIELDSA required field is missing.Verify that you provided values for Name, Type, Repository, Path, and README.
ARTIFACT_NOT_FOUNDThe specified artifact path doesn't exist in Artifactory/Package doesn't exist in repositoryVerify that the path to the artifact binary in JFrog Artifactory is correct.
INSUFFICIENT_PERMISSIONSYou don't have the required permissions for the project.Ensure you have READ access to the repository and ALLOW permission on the project
VIRTUAL_REPO_NOT_SUPPORTEDAttempted to use a virtual repositoryUse a local repository instead
REPO_PROJECT_MISMATCHRepository belongs to a different projectUse a repository owned by your project

Getting Help

If you continue to experience issues:

  • Collect the relevant log files from the affected device (e.g. Gateway or CLI logs).
  • Note any HTTP status codes and error messages from the UI or API.
  • Contact JFrog support with the collected information.