包版本 Mcp 服务器

什麼是 mcp-package-version？

mcp-package-version 是一個由用戶 ### sammcj 在 GitHub 上創建的倉庫。這個倉庫旨在管理和跟踪 MCP（多通道包）生態系統中的包版本。它是開發人員維護版本控制和確保不同包版本之間兼容性的重要工具。

mcp-package-version 的特點

版本控制：該倉庫允許用戶管理多個包版本，使得根據需要回滾或升級變得更容易。
兼容性跟踪：它有助於跟踪哪些包版本彼此兼容，減少衝突的風險。
公共訪問：作為一個公共倉庫，它允許其他開發人員進行協作和貢獻，增強包管理過程的整體功能和可靠性。
文檔：提供全面的文檔，幫助用戶了解如何有效使用該倉庫及其特點。

如何使用 mcp-package-version

克隆倉庫：首先使用以下命令將倉庫克隆到本地機器：
```
git clone https://github.com/sammcj/mcp-package-version.git
```
安裝依賴項：導航到克隆的目錄並安裝文檔中列出的任何必要依賴項。
管理版本：使用提供的命令添加、更新或刪除包版本。確保遵循版本控制指南以維持兼容性。
協作：如果您希望貢獻，請先分叉倉庫，進行更改，然後提交拉取請求以供審核。
保持更新：定期檢查倉庫的更新，以確保您使用的是最新的功能和修復。

常見問題解答

問題1：mcp-package-version 倉庫的目的是什么？

回答1：mcp-package-version 倉庫旨在幫助開發人員管理和跟踪 MCP 生態系統中的包版本，確保兼容性和易用性。

問題2：我如何能夠為 mcp-package-version 倉庫做出貢獻？

回答2：您可以通過分叉倉庫、進行更改並提交拉取請求來貢獻。請確保遵循文檔中提供的貢獻指南。

問題3：mcp-package-version 倉庫是否對公眾開放？

回答3：是的，該倉庫是公開的，任何人都可以訪問、使用和貢獻。

問題4：我可以在哪裡找到 mcp-package-version 的文檔？

回答4：文檔通常在倉庫內部提供，通常在 README.md 文件或專門的 docs 目錄中。

問題5：我如何在 mcp-package-version 倉庫中報告問題或錯誤？

回答5：您可以通過導航到倉庫中的“問題”選項卡並提交一個新問題，詳細說明問題來報告問題。

Package Version MCP Server

An MCP server that provides tools for checking latest stable package versions from multiple package registries:

npm (Node.js/JavaScript)
PyPI (Python)
Maven Central (Java)
Go Proxy (Go)
Swift Packages (Swift)
AWS Bedrock (AI Models)
Docker Hub (Container Images)
GitHub Container Registry (Container Images)
GitHub Actions

This server helps LLMs ensure they're recommending up-to-date package versions when writing code.

IMPORTANT: I'm slowly moving across this tool to a component of my mcp-devtools server

Screenshot

tooling with and without mcp-package-version

Package Version MCP Server

Installation

Requirements:

A modern go version installed (See Go Installation)

Using go install (Recommended for MCP Client Setup):

go install github.com/sammcj/mcp-package-version/v2@HEAD

Then setup your client to use the MCP server. Assuming you've installed the binary with go install github.com/sammcj/mcp-package-version/v2@HEAD and your $GOPATH is /Users/sammcj/go/bin, you can provide the full path to the binary:

{
  "mcpServers": {
    "package-version": {
      "command": "/Users/sammcj/go/bin/mcp-package-version"
    }
  }
}

For the Cline VSCode Extension this will be ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
For Claude Desktop ~/Library/Application\ Support/Claude/claude_desktop_config.json
For GoMCP ~/.config/gomcp/config.yaml

Other Installation Methods

Or clone the repository and build it:

git clone https://github.com/sammcj/mcp-package-version.git
cd mcp-package-version
make

You can also run the server in a container:

docker run -p 18080:18080 ghcr.io/sammcj/mcp-package-version:main

Note: If running in a container, you'll need to configure the client to use the URL instead of command, e.g.:

{
  "mcpServers": {
    "package-version": {
      "url": "http://localhost:18080",
    }
  }
}

Tip: Go Path

If $GOPATH/bin is not in your PATH, you'll need to provide the full path to the binary when configuring your MCP client (e.g. /Users/sammcj/go/bin/mcp-package-version).

If you haven't used go applications before and have only just installed go, you may not have a $GOPATH set up in your environment. This is important for any go install command to work correctly.

Understanding $GOPATH

The go install command downloads and compiles Go packages, placing the resulting binary executable in the bin subdirectory of your $GOPATH. By default, $GOPATH is > usually located at $HOME/go on Unix-like systems (including macOS). If you haven't configured $GOPATH explicitly, Go uses this default.

The location $GOPATH/bin (e.g., /Users/your_username/go/bin) needs to be included in your system's PATH environment variable if you want to run installed Go binaries directly by name from any terminal location.

You can add the following line to your shell configuration file (e.g., ~/.zshrc, ~/.bashrc) to set $GOPATH to the default if it's not already set, and ensure $GOPATH/bin is in your PATH:
[ -z "$GOPATH" ] && export GOPATH="$HOME/go"; echo "$PATH" | grep -q ":$GOPATH/bin" || export PATH="$PATH:$GOPATH/bin"
After adding this line, restart your terminal or MCP client.

Usage

The server supports two transport modes: stdio (default) and SSE (Server-Sent Events).

STDIO Transport (Default)

mcp-package-version

SSE Transport

mcp-package-version --transport sse --port 18080 --base-url "http://localhost:18080"

This would make the server available to clients at http://localhost:18080/sse (Note the /sse suffix!).

Command-line Options

--transport, -t: Transport type (stdio or sse). Default: stdio
--port: Port to use for SSE transport. Default: 18080
--base-url: Base URL for SSE transport. Default: http://localhost

Docker Images

Docker images are available from GitHub Container Registry:

docker pull ghcr.io/sammcj/mcp-package-version:main

You can also see the example docker-compose.yaml.

Tools

NPM Packages

Check the latest versions of NPM packages:

{
  "name": "check_npm_versions",
  "arguments": {
    "dependencies": {
      "react": "^17.0.2",
      "react-dom": "^17.0.2",
      "lodash": "4.17.21"
    },
    "constraints": {
      "react": {
        "majorVersion": 17
      }
    }
  }
}

Python Packages (requirements.txt)

Check the latest versions of Python packages from requirements.txt:

{
  "name": "check_python_versions",
  "arguments": {
    "requirements": [
      "requests==2.28.1",
      "flask>=2.0.0",
      "numpy"
    ]
  }
}

Python Packages (pyproject.toml)

Check the latest versions of Python packages from pyproject.toml:

{
  "name": "check_pyproject_versions",
  "arguments": {
    "dependencies": {
      "dependencies": {
        "requests": "^2.28.1",
        "flask": ">=2.0.0"
      },
      "optional-dependencies": {
        "dev": {
          "pytest": "^7.0.0"
        }
      },
      "dev-dependencies": {
        "black": "^22.6.0"
      }
    }
  }
}

Java Packages (Maven)

Check the latest versions of Java packages from Maven:

{
  "name": "check_maven_versions",
  "arguments": {
    "dependencies": [
      {
        "groupId": "org.springframework.boot",
        "artifactId": "spring-boot-starter-web",
        "version": "2.7.0"
      },
      {
        "groupId": "com.google.guava",
        "artifactId": "guava",
        "version": "31.1-jre"
      }
    ]
  }
}

Java Packages (Gradle)

Check the latest versions of Java packages from Gradle:

{
  "name": "check_gradle_versions",
  "arguments": {
    "dependencies": [
      {
        "configuration": "implementation",
        "group": "org.springframework.boot",
        "name": "spring-boot-starter-web",
        "version": "2.7.0"
      },
      {
        "configuration": "testImplementation",
        "group": "junit",
        "name": "junit",
        "version": "4.13.2"
      }
    ]
  }
}

Go Packages

Check the latest versions of Go packages from go.mod:

{
  "name": "check_go_versions",
  "arguments": {
    "dependencies": {
      "module": "github.com/example/mymodule",
      "require": [
        {
          "path": "github.com/gorilla/mux",
          "version": "v1.8.0"
        },
        {
          "path": "github.com/spf13/cobra",
          "version": "v1.5.0"
        }
      ]
    }
  }
}

Docker Images

Check available tags for Docker images:

{
  "name": "check_docker_tags",
  "arguments": {
    "image": "nginx",
    "registry": "dockerhub",
    "limit": 5,
    "filterTags": ["^1\\."],
    "includeDigest": true
  }
}

AWS Bedrock Models

List all AWS Bedrock models:

{
  "name": "check_bedrock_models",
  "arguments": {
    "action": "list"
  }
}

Search for specific AWS Bedrock models:

{
  "name": "check_bedrock_models",
  "arguments": {
    "action": "search",
    "query": "claude",
    "provider": "anthropic"
  }
}

Get the latest Claude Sonnet model:

{
  "name": "get_latest_bedrock_model",
  "arguments": {}
}

Swift Packages

Check the latest versions of Swift packages:

{
  "name": "check_swift_versions",
  "arguments": {
    "dependencies": [
      {
        "url": "https://github.com/apple/swift-argument-parser",
        "version": "1.1.4"
      },
      {
        "url": "https://github.com/vapor/vapor",
        "version": "4.65.1"
      }
    ],
    "constraints": {
      "https://github.com/apple/swift-argument-parser": {
        "majorVersion": 1
      }
    }
  }
}

GitHub Actions

Check the latest versions of GitHub Actions:

{
  "name": "check_github_actions",
  "arguments": {
    "actions": [
      {
        "owner": "actions",
        "repo": "checkout",
        "currentVersion": "v3"
      },
      {
        "owner": "actions",
        "repo": "setup-node",
        "currentVersion": "v3"
      }
    ],
    "includeDetails": true
  }
}

Releases and CI/CD

This project uses GitHub Actions for continuous integration and deployment. The workflow automatically:

Builds and tests the application on every push to the main branch and pull requests
Creates a release when a tag with the format v* (e.g., v1.0.0) is pushed
Builds and pushes Docker images to GitHub Container Registry

License

MIT

概覽

什麼是 mcp-package-version？

mcp-package-version 是一個由用戶 ### sammcj 在 GitHub 上創建的倉庫。這個倉庫旨在管理和跟踪 MCP（多通道包）生態系統中的包版本。它是開發人員維護版本控制和確保不同包版本之間兼容性的重要工具。

mcp-package-version 的特點

如何使用 mcp-package-version

常見問題解答

問題1：mcp-package-version 倉庫的目的是什么？

問題2：我如何能夠為 mcp-package-version 倉庫做出貢獻？

問題3：mcp-package-version 倉庫是否對公眾開放？

問題4：我可以在哪裡找到 mcp-package-version 的文檔？

問題5：我如何在 mcp-package-version 倉庫中報告問題或錯誤？

詳細

Package Version MCP Server

Screenshot

Installation

Other Installation Methods

Tip: Go Path

Usage

STDIO Transport (Default)

SSE Transport

Command-line Options

Docker Images

Tools

NPM Packages

Python Packages (requirements.txt)

Python Packages (pyproject.toml)

Java Packages (Maven)

Java Packages (Gradle)

Go Packages

Docker Images

AWS Bedrock Models

Swift Packages

GitHub Actions

Releases and CI/CD

License

伺服器配置

專案資訊

包版本 Mcp 服务器 替代方案

Llamacloud Mcp 伺服器

Deepseek 思考者 Mcp 伺服器

Mcp 伺服器用於 Asana

@reapi/mcp 開放API

Mcp 伺服器用於深入研究

Ramp Mcp: 一個 Ramp Mcp 伺服器

Strava Mcp 伺服器

Ns 旅行資訊 Mcp 伺服器

包版本 Mcp 服务器替代方案