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 environment and that your regex patterns are not inadvertently blocking the tools.
-
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 Registry.
-
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 IDE plugin? Uninstall the JFrog plugin from your IDE's plugin or extension manager. The MCP Gateway stops automatically when the plugin is removed.
-
How do I configure runtime arguments for a server?
You configure runtime arguments during the process of adding a server to the registry.
- When adding a server to the registry, proceed to Step 2: Configuration in the Add to Registry wizard.
- Click the Runtime arguments tab (next to the Environment variables tab) and enter your configuration.
- After saving, you can view the configured runtime arguments at any time on the Configuration tab of the MCP Server Details page.
-
How do I set environment variables as secrets?
- During Step 2 (Configuration) of the Add to Registry wizard, navigate to the Environment variables tab.
- Next to the specific environment variable you are configuring, click the Secret toggle to turn it on.
Troubleshooting Custom MCPs
The following table describes common errors that can occur during registration or unregistration of custom MCPs.
| Error | Cause | Resolution |
|---|---|---|
MISSING_MANDATORY_FIELDS | A required field is missing. | Verify that you provided values for Name, Type, Repository, Path, and README. |
ARTIFACT_NOT_FOUND | The specified artifact path does not exist in Artifactory or the package does not exist in the repository. | Verify that the path to the artifact binary in JFrog Artifactory is correct. |
INSUFFICIENT_PERMISSIONS | You do not have the required permissions for the project. | Ensure you have READ access to the repository and ALLOW permission on the project. |
VIRTUAL_REPO_NOT_SUPPORTED | Attempted to use a virtual repository. | Use a local repository instead. |
REPO_PROJECT_MISMATCH | Repository belongs to a different project. | Use a repository owned by your project. |
Getting Help
If you continue to experience issues:
- Collect the relevant log files from the affected device (for example, Gateway or CLI logs).
- Note any HTTP status codes and error messages from the UI or API.
- Contact JFrog support with the collected information.
Updated 18 days ago
