From 360f5d799ed63621bf830edd219b13044bc14c4b Mon Sep 17 00:00:00 2001 From: Liana Ertz <167086211+ertzL@users.noreply.github.com> Date: Thu, 19 Feb 2026 11:37:17 +0000 Subject: [PATCH 1/6] Create integrating-with-mcp --- src/content/integrations/integrating-with-mcp | 100 ++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 src/content/integrations/integrating-with-mcp diff --git a/src/content/integrations/integrating-with-mcp b/src/content/integrations/integrating-with-mcp new file mode 100644 index 00000000..4364c4d3 --- /dev/null +++ b/src/content/integrations/integrating-with-mcp @@ -0,0 +1,100 @@ +# MCP Server Support for Cloudsmith CLI + +The Cloudsmith CLI now includes support for the Model Context Protocol (MCP), allowing AI assistants like Claude to interact with your Cloudsmith repositories through natural language. + +## What's New + +The MCP server enables AI assistants to programmatically manage Cloudsmith repositories, packages, and artifacts by automatically generating tools from Cloudsmith's OpenAPI specification. + +## Requirements + +**Python 3.10 or later** is now required to use the Cloudsmith CLI. + +## Getting Started + +### Auto-Configure MCP Clients + +The CLI provides a command to facilitate the configuration of MCP clients: + +```bash +# Configure for default profile +$ cloudsmith mcp configure + +# Configure for specific profile +$ cloudsmith mcp configure -P my-profile +``` + +Currently supported MCP clients for auto-configuration: **Claude Desktop**, **Cursor**, **VS Code (Copilot)**, and **Gemini CLI**. + +### Manual Configuration + +Alternatively, you can manually configure the MCP server by modifying the JSON configuration file for your LLM client. + +For example, with **Claude Desktop on macOS**, the configuration file is located at: + +``` +~/Library/Application Support/Claude/claude_desktop_config.json +``` + +Example configuration: + +```json +{ + "mcpServers": { + "cloudsmith": { + "command": "cloudsmith", + "args": [ + "mcp", + "start" + ] + } + } +} +``` + +**Note:** The MCP server will be started automatically by your LLM client. You don't need to run `cloudsmith mcp start` manually. + +### Managing Available Tools + +Due to the large number of tools exposed by the MCP server, a limited subset is available by default to avoid filling the LLM's context window. + +**Disabled tool categories by default:** +`broadcasts, rates, packages_upload, packages_validate, user_token, user_tokens, webhooks, status, repos_ecdsa, repos_geoip, repos_gpg, repos_rsa, repos_x509, repos_upstream, orgs_openid, orgs_saml, orgs_invites, files, badges, quota, users_profile, workspaces_policies, storage_regions, entitlements, metrics_entitlements, metrics_packages, orgs_teams, repo_retention` + +### List Available Tools and Groups + +```bash +# Show all available tools +$ cloudsmith mcp list_tools -a + +# Show all tool groups +$ cloudsmith mcp list_groups -a +``` + +After reviewing the available tools and groups, you can customize which ones are exposed to your AI assistant. + +## Customizing Available Tools + +You can customize which tools are available by editing `~/.cloudsmith/config.ini`: + +```bash +[default] +mcp_allowed_tools=workspaces_policies_simulate_list +mcp_allowed_tool_groups=metrics +``` + +This configuration exposes: + +- Individual tools listed in `mcp_allowed_tools` +- All tools within the groups specified in `mcp_allowed_tool_groups` + +## Authentication + +The MCP server uses your existing Cloudsmith CLI credentials: + +- **API Keys**: Automatically used if configured +- **SSO**: Complete authentication via `cloudsmith auth` before starting the server, as MCP clients cannot trigger the SSO flow automatically + +## Multi-Profile Support + +Configure separate MCP server instances for different Cloudsmith profiles using the `-P` flag with the configure command. From e367fb88797f45a4d03109966e69df34ae568f77 Mon Sep 17 00:00:00 2001 From: Liana Ertz <167086211+ertzL@users.noreply.github.com> Date: Thu, 19 Feb 2026 11:39:11 +0000 Subject: [PATCH 2/6] Delete src/content/integrations/integrating-with-mcp --- src/content/integrations/integrating-with-mcp | 100 ------------------ 1 file changed, 100 deletions(-) delete mode 100644 src/content/integrations/integrating-with-mcp diff --git a/src/content/integrations/integrating-with-mcp b/src/content/integrations/integrating-with-mcp deleted file mode 100644 index 4364c4d3..00000000 --- a/src/content/integrations/integrating-with-mcp +++ /dev/null @@ -1,100 +0,0 @@ -# MCP Server Support for Cloudsmith CLI - -The Cloudsmith CLI now includes support for the Model Context Protocol (MCP), allowing AI assistants like Claude to interact with your Cloudsmith repositories through natural language. - -## What's New - -The MCP server enables AI assistants to programmatically manage Cloudsmith repositories, packages, and artifacts by automatically generating tools from Cloudsmith's OpenAPI specification. - -## Requirements - -**Python 3.10 or later** is now required to use the Cloudsmith CLI. - -## Getting Started - -### Auto-Configure MCP Clients - -The CLI provides a command to facilitate the configuration of MCP clients: - -```bash -# Configure for default profile -$ cloudsmith mcp configure - -# Configure for specific profile -$ cloudsmith mcp configure -P my-profile -``` - -Currently supported MCP clients for auto-configuration: **Claude Desktop**, **Cursor**, **VS Code (Copilot)**, and **Gemini CLI**. - -### Manual Configuration - -Alternatively, you can manually configure the MCP server by modifying the JSON configuration file for your LLM client. - -For example, with **Claude Desktop on macOS**, the configuration file is located at: - -``` -~/Library/Application Support/Claude/claude_desktop_config.json -``` - -Example configuration: - -```json -{ - "mcpServers": { - "cloudsmith": { - "command": "cloudsmith", - "args": [ - "mcp", - "start" - ] - } - } -} -``` - -**Note:** The MCP server will be started automatically by your LLM client. You don't need to run `cloudsmith mcp start` manually. - -### Managing Available Tools - -Due to the large number of tools exposed by the MCP server, a limited subset is available by default to avoid filling the LLM's context window. - -**Disabled tool categories by default:** -`broadcasts, rates, packages_upload, packages_validate, user_token, user_tokens, webhooks, status, repos_ecdsa, repos_geoip, repos_gpg, repos_rsa, repos_x509, repos_upstream, orgs_openid, orgs_saml, orgs_invites, files, badges, quota, users_profile, workspaces_policies, storage_regions, entitlements, metrics_entitlements, metrics_packages, orgs_teams, repo_retention` - -### List Available Tools and Groups - -```bash -# Show all available tools -$ cloudsmith mcp list_tools -a - -# Show all tool groups -$ cloudsmith mcp list_groups -a -``` - -After reviewing the available tools and groups, you can customize which ones are exposed to your AI assistant. - -## Customizing Available Tools - -You can customize which tools are available by editing `~/.cloudsmith/config.ini`: - -```bash -[default] -mcp_allowed_tools=workspaces_policies_simulate_list -mcp_allowed_tool_groups=metrics -``` - -This configuration exposes: - -- Individual tools listed in `mcp_allowed_tools` -- All tools within the groups specified in `mcp_allowed_tool_groups` - -## Authentication - -The MCP server uses your existing Cloudsmith CLI credentials: - -- **API Keys**: Automatically used if configured -- **SSO**: Complete authentication via `cloudsmith auth` before starting the server, as MCP clients cannot trigger the SSO flow automatically - -## Multi-Profile Support - -Configure separate MCP server instances for different Cloudsmith profiles using the `-P` flag with the configure command. From 2be50da5c5b9b63c3008767ba877b4219e93d1a9 Mon Sep 17 00:00:00 2001 From: Liana Ertz <167086211+ertzL@users.noreply.github.com> Date: Thu, 19 Feb 2026 11:40:19 +0000 Subject: [PATCH 3/6] Create integrating-with-mcp.mdx --- .../integrations/integrating-with-mcp.mdx | 100 ++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 src/content/integrations/integrating-with-mcp.mdx diff --git a/src/content/integrations/integrating-with-mcp.mdx b/src/content/integrations/integrating-with-mcp.mdx new file mode 100644 index 00000000..4364c4d3 --- /dev/null +++ b/src/content/integrations/integrating-with-mcp.mdx @@ -0,0 +1,100 @@ +# MCP Server Support for Cloudsmith CLI + +The Cloudsmith CLI now includes support for the Model Context Protocol (MCP), allowing AI assistants like Claude to interact with your Cloudsmith repositories through natural language. + +## What's New + +The MCP server enables AI assistants to programmatically manage Cloudsmith repositories, packages, and artifacts by automatically generating tools from Cloudsmith's OpenAPI specification. + +## Requirements + +**Python 3.10 or later** is now required to use the Cloudsmith CLI. + +## Getting Started + +### Auto-Configure MCP Clients + +The CLI provides a command to facilitate the configuration of MCP clients: + +```bash +# Configure for default profile +$ cloudsmith mcp configure + +# Configure for specific profile +$ cloudsmith mcp configure -P my-profile +``` + +Currently supported MCP clients for auto-configuration: **Claude Desktop**, **Cursor**, **VS Code (Copilot)**, and **Gemini CLI**. + +### Manual Configuration + +Alternatively, you can manually configure the MCP server by modifying the JSON configuration file for your LLM client. + +For example, with **Claude Desktop on macOS**, the configuration file is located at: + +``` +~/Library/Application Support/Claude/claude_desktop_config.json +``` + +Example configuration: + +```json +{ + "mcpServers": { + "cloudsmith": { + "command": "cloudsmith", + "args": [ + "mcp", + "start" + ] + } + } +} +``` + +**Note:** The MCP server will be started automatically by your LLM client. You don't need to run `cloudsmith mcp start` manually. + +### Managing Available Tools + +Due to the large number of tools exposed by the MCP server, a limited subset is available by default to avoid filling the LLM's context window. + +**Disabled tool categories by default:** +`broadcasts, rates, packages_upload, packages_validate, user_token, user_tokens, webhooks, status, repos_ecdsa, repos_geoip, repos_gpg, repos_rsa, repos_x509, repos_upstream, orgs_openid, orgs_saml, orgs_invites, files, badges, quota, users_profile, workspaces_policies, storage_regions, entitlements, metrics_entitlements, metrics_packages, orgs_teams, repo_retention` + +### List Available Tools and Groups + +```bash +# Show all available tools +$ cloudsmith mcp list_tools -a + +# Show all tool groups +$ cloudsmith mcp list_groups -a +``` + +After reviewing the available tools and groups, you can customize which ones are exposed to your AI assistant. + +## Customizing Available Tools + +You can customize which tools are available by editing `~/.cloudsmith/config.ini`: + +```bash +[default] +mcp_allowed_tools=workspaces_policies_simulate_list +mcp_allowed_tool_groups=metrics +``` + +This configuration exposes: + +- Individual tools listed in `mcp_allowed_tools` +- All tools within the groups specified in `mcp_allowed_tool_groups` + +## Authentication + +The MCP server uses your existing Cloudsmith CLI credentials: + +- **API Keys**: Automatically used if configured +- **SSO**: Complete authentication via `cloudsmith auth` before starting the server, as MCP clients cannot trigger the SSO flow automatically + +## Multi-Profile Support + +Configure separate MCP server instances for different Cloudsmith profiles using the `-P` flag with the configure command. From 4f2fb5628ba0f2d61eec60190f7421ef8b5b3d9d Mon Sep 17 00:00:00 2001 From: Liana Ertz <167086211+ertzL@users.noreply.github.com> Date: Thu, 19 Feb 2026 13:24:08 +0000 Subject: [PATCH 4/6] Update src/content/integrations/integrating-with-mcp.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- src/content/integrations/integrating-with-mcp.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/src/content/integrations/integrating-with-mcp.mdx b/src/content/integrations/integrating-with-mcp.mdx index 4364c4d3..9841e707 100644 --- a/src/content/integrations/integrating-with-mcp.mdx +++ b/src/content/integrations/integrating-with-mcp.mdx @@ -1,4 +1,5 @@ # MCP Server Support for Cloudsmith CLI +How to integrate MCP with Cloudsmith The Cloudsmith CLI now includes support for the Model Context Protocol (MCP), allowing AI assistants like Claude to interact with your Cloudsmith repositories through natural language. From d56040bed6d1f13eb0c950ed600a8908b7223711 Mon Sep 17 00:00:00 2001 From: Liana Ertz <167086211+ertzL@users.noreply.github.com> Date: Thu, 19 Feb 2026 13:25:24 +0000 Subject: [PATCH 5/6] Update src/content/integrations/integrating-with-mcp.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- src/content/integrations/integrating-with-mcp.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/integrations/integrating-with-mcp.mdx b/src/content/integrations/integrating-with-mcp.mdx index 9841e707..a1a801ea 100644 --- a/src/content/integrations/integrating-with-mcp.mdx +++ b/src/content/integrations/integrating-with-mcp.mdx @@ -9,7 +9,7 @@ The MCP server enables AI assistants to programmatically manage Cloudsmith repos ## Requirements -**Python 3.10 or later** is now required to use the Cloudsmith CLI. +**Python 3.10 or later** is required to use the Cloudsmith CLI. ## Getting Started From 46262fd0dca4b562df0f2a4f3d2703e59cab18c6 Mon Sep 17 00:00:00 2001 From: Liana Ertz <167086211+ertzL@users.noreply.github.com> Date: Thu, 19 Feb 2026 13:26:00 +0000 Subject: [PATCH 6/6] Update src/content/integrations/integrating-with-mcp.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- src/content/integrations/integrating-with-mcp.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/integrations/integrating-with-mcp.mdx b/src/content/integrations/integrating-with-mcp.mdx index a1a801ea..66c3d52a 100644 --- a/src/content/integrations/integrating-with-mcp.mdx +++ b/src/content/integrations/integrating-with-mcp.mdx @@ -94,7 +94,7 @@ This configuration exposes: The MCP server uses your existing Cloudsmith CLI credentials: - **API Keys**: Automatically used if configured -- **SSO**: Complete authentication via `cloudsmith auth` before starting the server, as MCP clients cannot trigger the SSO flow automatically +- **SSO**: Complete authentication via `cloudsmith auth` before configuring and launching your LLM client, as MCP clients cannot trigger the SSO flow automatically once the server is running ## Multi-Profile Support