Skip to content
Back to search

mcp-get

Archived: mcp-get is no longer maintained.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/michaellatman--mcp-get/badge.svg)](/listings/michaellatman--mcp-get)

HTML

<a href="/listings/michaellatman--mcp-get"><img src="/api/listings/michaellatman--mcp-get/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Try mcp-get immediately:

npx @michaellatman/mcp-get@latest list
npx @michaellatman/mcp-get@latest install @modelcontextprotocol/server-brave-search

All packages added to the registry are automatically displayed on [mcp-get.com](https://mcp-get.com), making them discoverable to other users.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 224 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # ⚠️ DEPRECATED - This Project Has Moved
  2. **This repository is no longer actively maintained.**
  3. We want to extend our heartfelt thanks to everyone who contributed to mcp-get, submitted packages, reported issues, and helped build this community. Your contributions and support have been invaluable in advancing the Model Context Protocol ecosystem.
  4. ## 🎯 Recommendation
  5. **We recommend [Smithery](https://smithery.ai)** for discovering, installing, and managing MCP servers.
  6. Smithery provides:
  7. - A comprehensive, curated registry of MCP servers
  8. - Simple installation and management
  9. - Better discovery and documentation
  10. - Active maintenance and support
  11. Visit **[smithery.ai](https://smithery.ai)** to get started.
  12. **Note:** This tool will continue to work, but will no longer receive updates or new features.
  13. ---
  14. # mcp-get (Archived)
  15. A powerful command-line tool for discovering, installing, and managing Model Context Protocol (MCP) servers. This tool simplifies the process of connecting Large Language Models (LLMs) to external data sources, tools, and services.
  16. With mcp-get, you can:
  17. - Discover available MCP servers from our curated registry
  18. - Install servers with a single command
  19. - Manage environment variables and configurations
  20. - Update and uninstall servers as needed
  21. ## Quick Start
  22. Try mcp-get immediately:
  23. ```bash
  24. npx @michaellatman/mcp-get@latest list
  25. npx @michaellatman/mcp-get@latest install @modelcontextprotocol/server-brave-search
  26. ```
  27. All packages added to the registry are automatically displayed on [mcp-get.com](https://mcp-get.com), making them discoverable to other users.
  28. ## About Model Context Protocol
  29. The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.
  30. Learn more about MCP at [modelcontextprotocol.io](https://modelcontextprotocol.io/introduction)
  31. ## What Packages Can You Install?
  32. This tool helps you install and manage MCP servers that connect Claude to various data sources and tools, including:
  33. - **Development Tools**: GitHub, GitLab
  34. - **Communication Tools**: Slack
  35. - **Search & Data**: Brave Search, Google Maps
  36. - **Database Systems**: PostgreSQL, SQLite
  37. - **Web Automation**: Puppeteer
  38. - **Cloud Storage**: Google Drive
  39. ## Prerequisites
  40. - Node.js (version 14 or higher) for Node.js-based MCP servers
  41. - Python (version 3.10 or higher) for Python-based MCP servers
  42. - Go (version 1.16 or higher) for Go-based MCP servers
  43. - Claude Desktop app (for local MCP server usage)
  44. ## Usage Examples
  45. ### Install a Package
  46. ```
  47. npx @michaellatman/mcp-get@latest install @modelcontextprotocol/server-brave-search
  48. ```
  49. Sample output:
  50. ```
  51. Installing @modelcontextprotocol/server-brave-search...
  52. Installation complete.
  53. ```
  54. #### Install a Specific Version
  55. You can also install a specific version of a package:
  56. ```
  57. npx @michaellatman/mcp-get@latest install @modelcontextprotocol/server-brave-search 1.0.0
  58. ```
  59. Sample output:
  60. ```
  61. Installing @modelcontextprotocol/server-brave-search version 1.0.0...
  62. Installation complete.
  63. ```
  64. The version syntax follows standard package manager conventions:
  65. - For Node.js packages: `package@version` (e.g., `@modelcontextprotocol/server-brave-search@1.0.0`)
  66. - For Python packages: `package==version` (e.g., `mcp-server-aidd==0.1.19`)
  67. - For Go packages: `package@version` (e.g., `example.com/go-server@v1.0.0`)
  68. ### List Packages
  69. ```
  70. npx @michaellatman/mcp-get@latest list
  71. ```
  72. Sample output:
  73. ```
  74. 📦 Available Packages
  75. Found 11 packages
  76. @modelcontextprotocol/server-brave-search │ MCP server for Brave Search API integration │ Anthropic, PBC (https://anthropic.com) │ MIT
  77. @modelcontextprotocol/server-everything │ MCP server that exercises all the features of the MCP protocol │ Anthropic, PBC (https://anthropic.com) │ MIT
  78. ...
  79. ```
  80. ### Uninstall a Package
  81. ```
  82. npx @michaellatman/mcp-get@latest uninstall @modelcontextprotocol/server-brave-search
  83. ```
  84. Sample output:
  85. ```
  86. Uninstalling @modelcontextprotocol/server-brave-search...
  87. Uninstallation complete.
  88. ```
  89. ### Update the Tool
  90. The tool automatically checks for updates when running commands. You can also manually update:
  91. ```
  92. npx @michaellatman/mcp-get@latest update
  93. ```
  94. Sample output:
  95. ```
  96. Updating mcp-get...
  97. Update complete.
  98. ```
  99. ## Contributing
  100. Thank you for your interest in contributing to mcp-get. This project is no
  101. longer maintained and does not accept new issues or pull requests.
  102. ## License
  103. This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details.
  104. ## Contact Information
  105. This repository is retained in read-only form for existing users.
  106. ## Adding Your Own MCP Server to the Registry
  107. There are two ways to add your MCP server to the registry:
  108. ### Option 1: Manual Package Addition
  109. If you want to maintain your own package:
  110. 1. **Create Your MCP Server**:
  111. - Develop your MCP server according to the [MCP protocol specifications](https://modelcontextprotocol.io)
  112. - Publish it as either an NPM package (installable via npm) or a Python package (installable via uvx)
  113. 2. **Add Your Package to the Package Folder**: Add your server as a JSON file in the `packages/` directory:
  114. - For regular packages, use `packages/your-package-name.json`
  115. - For scoped packages, use `packages/scope--package-name.json` (double hyphens between scope and name)
  116. ```json
  117. {
  118. "name": "your-package-name",
  119. "description": "A brief description of your MCP server",
  120. "vendor": "Your Name or Organization",
  121. "sourceUrl": "URL to the source code repository",
  122. "homepage": "URL to the homepage or documentation",
  123. "license": "License type (e.g., MIT)",
  124. "runtime": "node | python | go",
  125. "environmentVariables": {
  126. "SOME_API_KEY": {
  127. "description": "Description of what this key is for",
  128. "required": true
  129. }
  130. }
  131. }
  132. ```
  133. Important notes:
  134. - The `name` field must be the exact resolvable package name in npm or pip
  135. - The `runtime` field specifies how your package should be installed:
  136. - Use `"runtime": "node"` for packages that should be installed via npm
  137. - Use `"runtime": "python"` for packages that should be installed via uvx
  138. - Always include an `environmentVariables` object (can be empty `{}` if none required)
  139. 3. **Validate Your Package**: Run the PR check to validate your package:
  140. ```
  141. npm run pr-check
  142. ```
  143. 4. **Submit a Pull Request**: Fork this repository, add your package file, and submit a PR.
  144. ### Option 2: Community Servers Repository
  145. If you don't want to manage package deployment and distribution:
  146. 1. **Fork Community Repository**:
  147. - Fork [mcp-get/community-servers](https://github.com/mcp-get/community-servers)
  148. - This repository follows the same structure as the official MCP servers
  149. 2. **Add Your Server**:
  150. - Add your implementation to the `src` directory
  151. - Follow the existing patterns and structure
  152. - Include necessary documentation and tests
  153. 3. **Submit a Pull Request**:
  154. - Submit your PR to the community servers repository
  155. - Once merged, your server will be automatically added to the registry
  156. Both options require following the [MCP protocol specifications](https://modelcontextprotocol.io). Choose the option that best fits your needs:
  157. - Option 1 if you want full control over your package distribution
  158. - Option 2 if you want to avoid managing package deployment and distribution

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.