JFrog MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JFROG_URL | No | The JFrog or Artifactory base URL (e.g., https://example.jfrog.io or https://example.jfrog.io/artifactory). | |
| JFROG_CA_BUNDLE | No | Path to a custom CA bundle file for SSL verification. | |
| JFROG_LOG_LEVEL | No | Logging level (e.g., DEBUG, INFO, WARNING, ERROR). | INFO |
| JFROG_MAX_DEPTH | No | Maximum directory depth for tree and path listing. | 5 |
| JFROG_TRUST_ENV | No | Whether to trust proxy environment variables (HTTP_PROXY, HTTPS_PROXY). | false |
| JFROG_VERIFY_SSL | No | Whether to verify SSL certificates. | true |
| JFROG_ACCESS_TOKEN | No | Direct JFrog access token. Takes priority over JFROG_ACCESS_TOKEN_FILE when both are set. | |
| JFROG_MAX_AQL_LIMIT | No | Maximum limit for AQL queries. | 500 |
| JFROG_MAX_PAGE_SIZE | No | Maximum allowed page size. | 200 |
| JFROG_MCP_TRANSPORT | No | Transport mode: 'stdio' or 'streamable-http'. | stdio |
| JFROG_ACCESS_TOKEN_FILE | No | Path to a file containing the JFrog access token. | |
| JFROG_CACHE_TTL_SECONDS | No | Cache TTL in seconds. | 60 |
| JFROG_DEFAULT_PAGE_SIZE | No | Default page size for paginated results. | 50 |
| JFROG_REQUEST_TIMEOUT_SECONDS | No | Request timeout in seconds. | 20 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jfrog_pingA | Check JFrog URL and token authentication without returning secrets. |
| jfrog_capabilitiesA | Describe JFrog MCP limits, compatibility behavior, and enabled features. |
| jfrog_list_repositoriesA | List JFrog repositories with optional filters and cursor pagination. |
| jfrog_list_pathB | List files and folders under one JFrog repository path. |
| jfrog_get_item_infoB | Get metadata for one JFrog file or folder. |
| jfrog_get_item_propertiesA | Get properties for one JFrog file or folder. |
| jfrog_get_item_statsB | Get download statistics for one JFrog file or folder. |
| jfrog_get_treeB | Get a bounded file/folder tree using storage metadata traversal. |
| jfrog_find_filesB | Find files with generic filters and response shaping. |
| jfrog_latest_filesB | Find latest files by client-side modified timestamp sorting. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| jfrog_repositories | List JFrog repositories. |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: health check, capabilities, repository listing, path listing, item metadata, properties, stats, tree traversal, file search, and latest files. The only potential ambiguity is between get_item_info and get_item_properties, but the descriptions clarify that info is general metadata while properties are specific key-value pairs.
Most tools follow a consistent get_/list_/find_ verb-noun pattern (e.g., get_item_properties, list_repositories, find_files). Minor deviations exist: jfrog_ping and jfrog_capabilities are verb/noun alone, and jfrog_latest_files uses an adjective instead of a verb, but the overall style is coherent and predictable.
Ten tools is well within the ideal range for a focused MCP server. Each tool addresses a specific task within the artifact repository domain, and the count feels neither sparse nor overwhelming.
The toolset covers the read-only/query surface thoroughly: repository listing, path browsing, metadata, properties, statistics, tree traversal, file search, and recent files. It lacks write operations (create/update/delete), but the tools are clearly scoped to inspection and discovery, so the absence does not create dead ends for its apparent purpose.