Skip to main content
Glama
jfrog

JFrog MCP Server

Official
by jfrog

jfrog_create_remote_repository

Create a new remote repository in JFrog Artifactory to proxy and manage external package registries, enabling secure and efficient package storage and retrieval.

Instructions

Create a new remote repository in Artifactory to proxy external package registries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allowAnyHostAuthNo
assumedOfflinePeriodSecsNo
blackedOutNo
blockMismatchingMimeTypesNo
blockPushingSchema1No
bypassHeadRequestsNo
cdnRedirectNo
clientTlsCertificateNo
composerRegistryUrlNohttps://packagist.org
contentSynchronisationNo
descriptionNoRepository description
disableProxyNo
disableUrlNormalizationNo
downloadContextPathNo
downloadRedirectNo
enableCookieManagementNo
enableTokenAuthenticationNo
environmentsNoEnvironments to assign the repository to
excludesPatternNo
externalDependenciesEnabledNo
externalDependenciesPatternsNo
feedContextPathNo
fetchJarsEagerlyNo
fetchSourcesEagerlyNo
forceConanAuthenticationNo
forceNugetAuthenticationNo
forceP2AuthenticationNo
gitRegistryUrlNohttps://github.com/rust-lang/crates.io-index
handleReleasesNo
handleSnapshotsNo
hardFailNo
includesPatternNo**/*
keyYesthe key of the repository
listRemoteFolderItemsNo
localAddressNo
maxUniqueSnapshotsNo
metadataRetrievalTimeoutSecsNo
missedRetrievalCachePeriodSecsNo
notesNoInternal notes
offlineNo
packageTypeYesPackage type of the repository
passwordNoRemote repository password
priorityResolutionNo
projectKeyNoProject key to assign the repository to
propertySetsNo
proxyNoProxy key from Artifactory
pyPIRegistryUrlNohttps://pypi.org
rclassYesThe repository type
remoteRepoChecksumPolicyTypeNogenerate-if-absent
remoteRepoLayoutRefNo
repoLayoutRefNo
retrievalCachePeriodSecsNo
shareConfigurationNo
socketTimeoutMillisNo
storeArtifactsLocallyNo
suppressPomConsistencyChecksNo
synchronizePropertiesNo
unusedArtifactsCleanupPeriodHoursNo
urlYesURL to the remote repository
usernameNoRemote repository username
v3FeedUrlNo
vcsGitDownloadUrlNo
vcsGitProviderNoGITHUB
vcsTypeNoGIT
xrayIndexNo

Implementation Reference

  • Core handler function that performs the HTTP PUT request to create a remote repository in JFrog Artifactory, handling default URL fallback and response parsing.
    export async function createRemoteRepository(options: z.infer<typeof CreateRemoteRepoSchema>) {
      // If packageType is provided but URL is not, use default URL from packageType defaults
      if (options.packageType && !options.url) {
        options.url = defaultModels[options.packageType] || "";
      }
    
      const response = await jfrogRequest(`/artifactory/api/repositories/${options.key}`, {
        method: "PUT",
        body: options
      });
         
      return JFrogRepositoryCreateResponseSchema.parse(response);
    }
  • Tool registration object defining the MCP tool 'jfrog_create_remote_repository' with its name, description, input schema, and thin handler wrapper.
    const createRemoteRepositoryTool = {
      name: "jfrog_create_remote_repository",
      description: "Create a new remote repository in Artifactory to proxy external package registries",
      inputSchema: zodToJsonSchema(CreateRemoteRepoSchema),
      //outputSchema: zodToJsonSchema(JFrogRepositoryCreateResponseSchema),
      handler: async (args: any) => {
        const parsedArgs = CreateRemoteRepoSchema.parse(args);
        return await createRemoteRepository(parsedArgs);
      }
    };
  • Input schema validation using Zod for the remote repository creation parameters, extending BaseRepositorySchema with remote-specific configurations.
    export const CreateRemoteRepoSchema = BaseRepositorySchema.extend({
      rclass: z.literal("remote").describe("The repository type"),
      url: z.string().describe("URL to the remote repository"),
      username: z.string().optional().describe("Remote repository username"),
      password: z.string().optional().describe("Remote repository password"),
      proxy: z.string().optional().describe("Proxy key from Artifactory"),
      disableProxy: z.boolean().default(false),
      notes: z.string().optional().describe("Internal notes"),
      includesPattern: z.string().default("**/*"),
      excludesPattern: z.string().default(""),
      repoLayoutRef: z.string().optional(),
      remoteRepoLayoutRef: z.string().default(""),
      remoteRepoChecksumPolicyType: RemoteChecksumPolicyEnum,
      handleReleases: z.boolean().default(true),
      handleSnapshots: z.boolean().default(true),
      maxUniqueSnapshots: z.number().default(0),
      suppressPomConsistencyChecks: z.boolean().default(false),
      hardFail: z.boolean().default(false),
      offline: z.boolean().default(false),
      blackedOut: z.boolean().default(false),
      storeArtifactsLocally: z.boolean().default(true),
      socketTimeoutMillis: z.number().default(15000),
      localAddress: z.string().optional(),
      retrievalCachePeriodSecs: z.number().default(7200),
      missedRetrievalCachePeriodSecs: z.number().default(1800),
      unusedArtifactsCleanupPeriodHours: z.number().default(0),
      assumedOfflinePeriodSecs: z.number().default(300),
      fetchJarsEagerly: z.boolean().default(false),
      fetchSourcesEagerly: z.boolean().default(false),
      shareConfiguration: z.boolean().default(false),
      synchronizeProperties: z.boolean().default(false),
      blockMismatchingMimeTypes: z.boolean().default(true),
      xrayIndex: z.boolean().default(false),
      propertySets: z.array(z.string()).optional(),
      allowAnyHostAuth: z.boolean().default(false),
      enableCookieManagement: z.boolean().default(false),
      enableTokenAuthentication: z.boolean().default(false),
      forceNugetAuthentication: z.boolean().default(false),
      forceP2Authentication: z.boolean().default(false),
      forceConanAuthentication: z.boolean().default(false),
      metadataRetrievalTimeoutSecs: z.number().default(60),
      gitRegistryUrl: z.string().default("https://github.com/rust-lang/crates.io-index"),
      composerRegistryUrl: z.string().default("https://packagist.org"),
      pyPIRegistryUrl: z.string().default("https://pypi.org"),
      vcsType: VcsTypeEnum,
      vcsGitProvider: VcsGitProviderEnum,
      vcsGitDownloadUrl: z.string().default(""),
      bypassHeadRequests: z.boolean().default(false),
      clientTlsCertificate: z.string().default(""),
      externalDependenciesEnabled: z.boolean().default(false),
      externalDependenciesPatterns: z.array(z.string()).optional(),
      downloadRedirect: z.boolean().default(false),
      cdnRedirect: z.boolean().default(false),
      feedContextPath: z.string().optional(),
      downloadContextPath: z.string().optional(),
      v3FeedUrl: z.string().optional(),
      listRemoteFolderItems: z.boolean().default(false),
      contentSynchronisation: ContentSyncSchema.optional(),
      blockPushingSchema1: z.boolean().default(false),
      priorityResolution: z.boolean().default(false),
      disableUrlNormalization: z.boolean().default(false)
    });
  • Export of RepositoryTools array including the jfrog_create_remote_repository tool for aggregation.
    export const RepositoryTools =[ 
      checkJfrogAvailabilityTool,
      createLocalRepositoryTool,
      createRemoteRepositoryTool,
      createVirtualRepositoryTool,
      setFolderPropertyTool,
      listRepositoriesTool
    ];
  • tools/index.ts:13-23 (registration)
    Main tools array aggregation including ...RepositoryTools, exposing the tool to the MCP server.
    export const tools =[
      ...RepositoryTools,
      ...BuildsTools,
      ...RuntimeTools,
      ...AccessTools,
      ...AQLTools,
      ...CatalogTools,
      ...CurationTools,
      ...PermissionsTools,
      ...ArtifactSecurityTools,
    ];
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions creation and proxying but lacks critical details like required permissions, whether this is a mutating operation, potential side effects, error handling, or rate limits. For a complex creation tool with 65 parameters, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high complexity (65 parameters, nested objects, no output schema, and low schema coverage), the description is insufficient. It doesn't address behavioral aspects, parameter meanings, or usage context, leaving the agent poorly equipped to handle this tool effectively. The conciseness comes at the cost of completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, meaning most parameters are undocumented in the schema. The description adds no parameter-specific information beyond the general purpose, failing to compensate for the low coverage. It doesn't explain key parameters like 'key', 'packageType', or 'url' beyond what little the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a new remote repository') and the resource ('in Artifactory'), with the specific purpose 'to proxy external package registries'. It distinguishes from sibling tools like 'jfrog_create_local_repository' and 'jfrog_create_virtual_repository' by specifying 'remote', though it doesn't explicitly contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like local or virtual repositories, nor does it mention prerequisites such as required permissions or system configuration. It states the purpose but offers no contextual usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jfrog/mcp-jfrog'

If you have feedback or need assistance with the MCP directory API, please join our Discord server