Add serverless framework MCP server configuration

- Introduced a new JSON configuration file for the Serverless Framework MCP server.
- Included metadata such as name, description, repository, author, and license.
- Defined installation methods for npm and CLI with necessary environment variables.
- Specified required arguments for AWS credentials.
- Added tools for creating, deploying, invoking functions, listing functions, retrieving logs, and removing services.
- Provided example prompts for common operations.

Author: dima-m711

README.md

@@ -23,7 +23,7 @@ MCPM is an open source service and a CLI package management tool for MCP servers
 
 ## 🤝 Community Contributions
 
-> 💡 **Grow the MCP ecosystem!** We welcome contributions to our [MCP Registry](mcp-registry/README.md). Add your own servers, improve documentation, or suggest features. Open source thrives with community participation!
+> 💡 **Internal MCP Registry!** This project includes an [Internal MCP Registry](mcp-registry/README.md) with 9 curated and tested MCP servers. The registry provides reliable, verified servers for production use. Community contributions to the main MCPM tool are welcome!
 
 ## 🚀 Quick Installation
 
@@ -153,9 +153,9 @@ mcpm config clear-cache          # Clear MCPM's registry cache. Cache defaults t
 mcpm inspector                   # Launch the MCPM Inspector UI to examine server configs
 ```
 
-### 📚 Registry
+### 📚 Internal Registry
 
-The MCP Registry is a central repository of available MCP servers that can be installed using MCPM. The registry is available at [mcpm.sh/registry](https://mcpm.sh/registry).
+This project includes an internal MCP Registry with 9 curated and tested MCP servers that can be installed using MCPM. The internal registry contains reliable servers for production use, including both internal (Melio) and verified external servers.
 
 ## 🗺️ Roadmap
 

mcp-registry/README.md

@@ -1,10 +1,10 @@
-# 📚 MCP Server Registry
+# 🔧 Internal MCP Installer
 
-The MCP Server Registry is a central repository of [Model Context Protocol](https://modelcontextprotocol.github.io/) servers. This registry enables easy discovery and installation of MCP servers for clients like Claude Desktop, Cursor, and Windsurf.
+This is an internal MCP (Model Context Protocol) installer containing a curated set of 9 supported MCP servers. This installer provides reliable, tested MCP servers for use with clients like Claude Desktop, Cursor, and Windsurf.
 
 <div align="center">
-<img src="https://img.shields.io/badge/Status-Active-brightgreen" alt="Status: Active">
-<img src="https://img.shields.io/badge/Contributions-Welcome-blue" alt="Contributions: Welcome">
+<img src="https://img.shields.io/badge/Status-Internal-orange" alt="Status: Internal">
+<img src="https://img.shields.io/badge/Servers-9-blue" alt="Servers: 9">
 </div>
 
 ## 🤔 What is MCP?
@@ -15,65 +15,81 @@ Model Context Protocol (MCP) is a standard for building LLM-powered tools. It en
 - 🧩 **Composable**: Mix and match tools from different providers
 - 🚀 **Portable**: Works across different clients and environments
 
-## 🧰 How to Use This Registry
+## 📦 Supported MCP Servers
 
-### 🔍 Browsing Servers
+This internal installer includes the following 9 curated MCP servers:
 
-Browse the `servers` directory to find MCP servers that match your needs. Each server has its own directory with:
+### Internal Servers (Melio)
+- **atlassian.json** - Atlassian/Jira integration tools
+- **figma.json** - Figma design tool integration
+- **mysql.json** - MySQL database operations
 
-- 📄 `[server-name].json` - Configuration details including endpoint, capabilities, and version
-- 📝 `README.md` - Documentation with usage examples and requirements
-- 🧪 Examples folder (optional)
+### External Servers (Verified)
+- **aws.json** - AWS cloud services integration (awslabs)
+- **circleci.json** - CircleCI CI/CD pipeline integration (CircleCI-Public)
+- **github.json** - GitHub repository and issue management (github)
+- **notion-mcp.json** - Notion workspace integration (makenotion)
+- **playwright-mcp.json** - Browser automation and testing (microsoft)
+- **serverless.json** - Serverless framework operations (serverless)
 
-### ⬇️ Installing Servers
-
-You can install servers from this registry using:
+## 🧰 How to Use This Installer
 
-1. **[MCPM](https://github.com/pathintegral-institute/mcpm.sh)**: Our recommended tool
-   ```bash
-   # Install a server by name
-   mcpm add server-name
-   ```
+### 🔍 Browsing Available Servers
 
-2. **Manual Configuration**: Add the server URL directly to your MCP client's configuration
+Browse the `servers/` directory to find the 9 supported MCP servers. Each server configuration file (`*.json`) contains:
 
-## 🤝 Contributing Your Server
+- 📄 Server metadata and configuration details
+- 🔗 Installation endpoints and version information
+- 🏷️ Categorization and capability descriptions
 
-We welcome contributions! There are two ways to add your server to the registry:
+### ⬇️ Installing Servers
 
-### 1. Create a GitHub Issue (Easiest)
+Install servers using [MCPM](https://github.com/pathintegral-institute/mcpm.sh):
 
-Simply create a [new GitHub issue](https://github.com/pathintegral-institute/mcp-registry/issues/new) with:
+```bash
+# Install a server by name
+mcpm add server-name
 
-- Title: "Add server: [your-server-name]"
-- Body: URL to your server details or API documentation
-- We'll automatically generate the necessary files and create a PR for you
+# Examples:
+mcpm add atlassian
+mcpm add github
+mcpm add playwright-mcp
+```
 
-### 2. Submit a Pull Request
+Alternatively, you can manually configure servers using the URLs and settings from the JSON files.
 
-For more control over your submission:
+## 🏗️ Server Categories
 
-1. Fork this repository
-2. Create a new directory in `servers/` with your server name
-3. Add your `manifest.json` following our [schema](schema/manifest-schema.json)
-4. Submit a pull request
+Our 9 supported servers are organized by functionality:
 
-For detailed instructions, see the [Contributing Guidelines](CONTRIBUTING.md).
+- **Development Tools**: github, circleci, playwright-mcp, serverless
+- **Design & Productivity**: figma, notion-mcp
+- **Infrastructure**: aws, mysql
+- **Project Management**: atlassian
 
 ## 📂 Registry Structure
 
 ```
 mcp-registry/
-├── README.md               # Overview, usage instructions
-├── CONTRIBUTING.md         # Guidelines for contributing servers
-├── servers/                # Directory containing all registered servers
-│   ├── [server-name]/      # Directory for each server
-│   │   ├── manifest.json   # Server metadata and configuration
-│   │   └── README.md       # Detailed server documentation
+├── README.md               # This file - overview and usage
+├── servers/                # 9 supported MCP server configurations
+│   ├── atlassian.json      # Atlassian/Jira integration
+│   ├── aws.json           # AWS cloud services
+│   ├── circleci.json      # CircleCI CI/CD
+│   ├── figma.json         # Figma design tools
+│   ├── github.json        # GitHub integration
+│   ├── mysql.json         # MySQL database
+│   ├── notion-mcp.json    # Notion workspace
+│   ├── playwright-mcp.json # Browser automation
+│   └── serverless.json    # Serverless framework
 └── schema/                 # Schema definitions
-    └── manifest-schema.json  # JSON Schema for manifest validation
+    └── server-schema.json  # JSON Schema for server validation
 ```
 
+## 🔄 Updates and Maintenance
+
+This internal installer is maintained with a fixed set of 9 verified MCP servers. Updates to server configurations are applied through controlled releases to ensure compatibility and reliability.
+
 ## 📜 License
 
-This registry is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
+This internal installer is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

mcp-registry/servers/atlassian.json

@@ -1,102 +1,140 @@
 {
-  "name": "atlassian",
-  "display_name": "Atlassian",
-  "description": "Interact with Atlassian Cloud products (Confluence and Jira) including searching/reading Confluence spaces/pages, accessing Jira issues, and project metadata.",
+  "name": "mcp-atlassian",
+  "display_name": "Atlassian MCP Server",
+  "description": "Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). This integration supports both Confluence & Jira Cloud and Server/Data Center deployments.",
   "repository": {
     "type": "git",
-    "url": "https://github.com/sooperset/mcp-atlassian"
+    "url": "https://github.com/melio/mcp-atlassian"
   },
-  "homepage": "https://github.com/sooperset/mcp-atlassian",
+  "homepage": "https://github.com/melio/mcp-atlassian",
   "author": {
-    "name": "sooperset"
+    "name": "melio"
   },
   "license": "MIT",
   "categories": [
+    "Professional Apps",
     "Productivity"
   ],
   "tags": [
-    "Atlassian",
-    "Confluence",
-    "Jira"
+    "atlassian",
+    "jira",
+    "confluence",
+    "api",
+    "model-context-protocol",
+    "integration"
   ],
   "installations": {
     "uvx": {
       "type": "uvx",
       "command": "uvx",
       "args": [
-        "mcp-atlassian",
-        "--confluence-url=${CONFLUENCE_URL}",
-        "--confluence-username=${CONFLUENCE_USERNAME}",
-        "--confluence-token=${CONFLUENCE_TOKEN}",
-        "--jira-url=${JIRA_URL}",
-        "--jira-username=${JIRA_USERNAME}",
-        "--jira-token=${JIRA_TOKEN}"
+        "mcp-atlassian"
       ],
-      "description": "Run with uvx (requires uv install)"
-    },
-    "python": {
-      "type": "python",
-      "command": "python",
-      "args": [
-        "-m",
-        "mcp-atlassian",
-        "--confluence-url=${CONFLUENCE_URL}",
-        "--confluence-username=${CONFLUENCE_USERNAME}",
-        "--confluence-token=${CONFLUENCE_TOKEN}",
-        "--jira-url=${JIRA_URL}",
-        "--jira-username=${JIRA_USERNAME}",
-        "--jira-token=${JIRA_TOKEN}"
-      ],
-      "description": "Run with Python module (requires pip install)"
-    },
-    "docker": {
-      "type": "docker",
-      "command": "docker",
-      "args": [
-        "run",
-        "--rm",
-        "-i",
-        "mcp/atlassian",
-        "--confluence-url=${CONFLUENCE_URL}",
-        "--confluence-username=${CONFLUENCE_USERNAME}",
-        "--confluence-token=${CONFLUENCE_TOKEN}",
-        "--jira-url=${JIRA_URL}",
-        "--jira-username=${JIRA_USERNAME}",
-        "--jira-token=${JIRA_TOKEN}"
-      ]
+      "env": {
+        "JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
+        "JIRA_USERNAME": "${JIRA_USERNAME}",
+        "JIRA_INSTANCE_URL": "${JIRA_INSTANCE_URL}"
+      },
+      "description": "Using uvx to run the Atlassian MCP server",
+      "recommended": true
     }
   },
   "arguments": {
-    "CONFLUENCE_URL": {
-      "description": "The URL of the Confluence site to connect to. Required for both Cloud and Server/Data Center deployments.",
+    "JIRA_API_TOKEN": {
+      "description": "Jira API token for authentication",
       "required": true,
-      "example": "https://your-company.atlassian.net/wiki or https://confluence.your-company.com"
+      "example": "your-jira-api-token"
     },
-    "CONFLUENCE_USERNAME": {
-      "description": "The username for the Confluence account (email for Cloud). Required to authenticate with Confluence.",
+    "JIRA_USERNAME": {
+      "description": "Jira username (email address)",
       "required": true,
-      "example": "your.email@company.com"
+      "example": "user@example.com"
     },
-    "CONFLUENCE_TOKEN": {
-      "description": "The API token or personal access token for the Confluence account. Required for authentication with Confluence.",
+    "JIRA_INSTANCE_URL": {
+      "description": "Jira instance URL",
       "required": true,
-      "example": "your_api_token or your_token"
+      "example": "https://your-domain.atlassian.net"
+    }
+  },
+  "tools": [
+    {
+      "name": "jira_search",
+      "description": "Search Jira issues using JQL (Jira Query Language)",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "jql": {
+            "type": "string",
+            "description": "JQL query string"
+          },
+          "fields": {
+            "type": "string",
+            "description": "Comma-separated fields to return"
+          },
+          "limit": {
+            "type": "integer",
+            "description": "Maximum number of results"
+          }
+        },
+        "required": ["jql"]
+      }
     },
-    "JIRA_URL": {
-      "description": "The URL of the Jira site to connect to. Required for both Cloud and Server/Data Center deployments.",
-      "required": true,
-      "example": "https://your-company.atlassian.net or https://jira.your-company.com"
+    {
+      "name": "jira_get_issue",
+      "description": "Get details of a specific Jira issue",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "issue_key": {
+            "type": "string",
+            "description": "Jira issue key (e.g., 'PROJ-123')"
+          }
+        },
+        "required": ["issue_key"]
+      }
     },
-    "JIRA_USERNAME": {
-      "description": "The username for the Jira account (email for Cloud). Required to authenticate with Jira.",
-      "required": true,
-      "example": "[email protected]"
+    {
+      "name": "jira_create_issue",
+      "description": "Create a new Jira issue",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "project_key": {
+            "type": "string",
+            "description": "The JIRA project key"
+          },
+          "summary": {
+            "type": "string",
+            "description": "Summary/title of the issue"
+          },
+          "issue_type": {
+            "type": "string",
+            "description": "Issue type (e.g., 'Task', 'Bug', 'Story')"
+          },
+          "description": {
+            "type": "string",
+            "description": "Issue description"
+          }
+        },
+        "required": ["project_key", "summary", "issue_type"]
+      }
+    }
+  ],
+  "examples": [
+    {
+      "title": "Search for issues",
+      "description": "Search for Jira issues using JQL",
+      "prompt": "Search for all open issues assigned to me"
     },
-    "JIRA_TOKEN": {
-      "description": "The API token or personal access token for the Jira account. Required for authentication with Jira.",
-      "required": true,
-      "example": "your_api_token or your_token"
+    {
+      "title": "Get issue details",
+      "description": "Get detailed information about a specific Jira issue",
+      "prompt": "Get details for issue PROJ-123"
+    },
+    {
+      "title": "Create new issue",
+      "description": "Create a new Jira issue",
+      "prompt": "Create a new bug report for the login functionality"
     }
-  },
-  "tools": []
+  ]
 }