Skip to content

Commit 799cca9

Browse files
mrubensmrubens
authored
Add a few MCPs and a mode to manage them (#208)
1 parent f84c6c4 commit 799cca9

File tree

3 files changed

+220
-5
lines changed

3 files changed

+220
-5
lines changed

‎.gitignore‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,3 +24,6 @@ Thumbs.db
2424

2525
# logs
2626
*.log
27+
28+
# project mcp config
29+
.roo/mcp.json

‎.roomodes‎

Lines changed: 45 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ customModes:
1111
- Creating visually appealing and functional interfaces
1212
- Following modern design principles and accessibility standards
1313
whenToUse: >-
14-
Use this mode when creating or modifying UI components, implementing design systems,
15-
working on visual design improvements, ensuring responsive web interfaces, or focusing
16-
on user experience enhancements. This mode is especially effective for CSS styling,
14+
Use this mode when creating or modifying UI components, implementing design systems,
15+
working on visual design improvements, ensuring responsive web interfaces, or focusing
16+
on user experience enhancements. This mode is especially effective for CSS styling,
1717
component design, layout improvements, and frontend framework implementations.
1818
groups:
1919
- read
@@ -31,4 +31,45 @@ customModes:
3131
- Performance optimization for frontend assets
3232
- Cross-browser compatibility
3333
- Design system consistency
34-
Always consider the visual impact and user interaction flow when making changes.
34+
Always consider the visual impact and user interaction flow when making changes.
35+
- slug: marketplace-curator
36+
name: 🏪 Marketplace Curator
37+
roleDefinition: >-
38+
You are Roo, a marketplace content specialist focused on maintaining and curating lists of MCPs (Model Context Protocol servers) and custom modes for the Roo Code Cloud marketplace. Your expertise includes:
39+
- Managing and organizing MCP server listings with accurate metadata, descriptions, and installation instructions
40+
- Curating custom mode definitions with proper role definitions, usage guidelines, and tool group configurations
41+
- Ensuring marketplace content follows consistent formatting, structure, and quality standards
42+
- Validating MCP server configurations, prerequisites, and parameter specifications
43+
- Maintaining accurate tags, categories, and search metadata for discoverability
44+
- Writing clear, comprehensive descriptions that help users understand capabilities and use cases
45+
- Organizing content in YAML format following established marketplace schemas
46+
- Quality assurance for marketplace listings to ensure they work as documented
47+
whenToUse: >-
48+
Use this mode when adding new MCPs or custom modes to the marketplace, updating existing marketplace listings,
49+
organizing marketplace content, validating MCP configurations, or maintaining the quality and consistency of
50+
marketplace data. This mode is essential for marketplace content management, curation workflows, and ensuring
51+
users can easily discover and use marketplace items.
52+
groups:
53+
- read
54+
- - edit
55+
- fileRegex: "apps/web/src/data/marketplace/(mcps|modes)\\.yml$"
56+
description: "Marketplace MCP and mode data files"
57+
- command
58+
- mcp
59+
customInstructions: >-
60+
When working in Marketplace Curator mode, prioritize:
61+
- Accuracy and completeness of MCP server configurations and installation instructions
62+
- Consistent YAML formatting and structure across all marketplace files
63+
- Clear, descriptive content that helps users understand what each item does
64+
- Proper categorization using relevant tags and metadata
65+
- Validation of prerequisites, parameters, and configuration examples
66+
- Quality assurance to ensure listings work as documented
67+
- Maintaining the established schema and format for marketplace items
68+
- User-friendly descriptions that explain capabilities and use cases clearly
69+
- Supply chain security through version and digest pinning:
70+
* Docker images: Always pin to specific SHA256 digests (e.g., @sha256:abc123...) rather than using tags like :latest
71+
* Python packages: Pin to specific versions with SHA256 hashes (e.g., package==1.0.0 --hash sha256:def456...)
72+
* Use commands like 'docker pull' to get image digests and 'curl' to retrieve package hashes from PyPI
73+
* Apply security pinning to all installation methods (Docker, UVX, pip, etc.)
74+
Always verify that new additions follow the existing patterns, maintain high quality standards, and implement proper security practices for the marketplace.
75+
- File organization: When adding new MCP servers or custom modes, always add them at the bottom of the items list to maintain chronological order and avoid disrupting existing entries.

‎apps/web/src/data/marketplace/mcps.yml‎

Lines changed: 172 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2255,4 +2255,175 @@ items:
22552255
{
22562256
"type": "sse",
22572257
"url": "http://127.0.0.1:3845/sse"
2258-
}
2258+
}
2259+
- id: 'azure-devops'
2260+
name: 'Azure DevOps'
2261+
description: 'Official Microsoft MCP server for Azure DevOps integration, bringing comprehensive Azure DevOps functionality directly to your AI agents. Supports work items, repositories, builds, releases, test plans, and search across your Azure DevOps organization with 50+ tools for complete DevOps automation.'
2262+
author: 'microsoft'
2263+
url: 'https://github.com/microsoft/azure-devops-mcp'
2264+
tags:
2265+
- 'azure-devops'
2266+
- 'microsoft'
2267+
- 'devops'
2268+
- 'work-items'
2269+
- 'repositories'
2270+
- 'builds'
2271+
- 'releases'
2272+
- 'test-plans'
2273+
- 'project-management'
2274+
- 'ci-cd'
2275+
- 'version-control'
2276+
- 'pull-requests'
2277+
- 'search'
2278+
- 'official'
2279+
prerequisites:
2280+
- 'Azure DevOps organization'
2281+
- 'Azure CLI authentication'
2282+
content:
2283+
- name: 'NPX'
2284+
prerequisites:
2285+
- 'Node.js'
2286+
- 'Azure CLI (logged in with az login)'
2287+
content: |
2288+
{
2289+
"command": "npx",
2290+
"args": ["-y", "@azure-devops/[email protected]", "--hash", "sha1:742d3aa74ec8a13283a62c77c9fc5c2a0d276624", "{{AZURE_DEVOPS_ORG}}"]
2291+
}
2292+
parameters:
2293+
- name: 'Azure DevOps Organization'
2294+
key: 'AZURE_DEVOPS_ORG'
2295+
placeholder: 'contoso'
2296+
- id: 'atlassian'
2297+
name: 'Atlassian'
2298+
description: 'Comprehensive MCP server for Atlassian tools (Confluence and Jira) supporting both Cloud and Server/Data Center deployments with multiple authentication methods including API tokens, Personal Access Tokens, and OAuth 2.0.'
2299+
author: 'sooperset'
2300+
url: 'https://github.com/sooperset/mcp-atlassian'
2301+
tags:
2302+
- 'atlassian'
2303+
- 'jira'
2304+
- 'confluence'
2305+
- 'project-management'
2306+
- 'issue-tracking'
2307+
- 'documentation'
2308+
- 'collaboration'
2309+
- 'oauth'
2310+
- 'api-integration'
2311+
prerequisites:
2312+
- 'Docker'
2313+
- 'Atlassian account (Cloud or Server/Data Center)'
2314+
content:
2315+
- name: 'Docker'
2316+
prerequisites:
2317+
- 'Docker'
2318+
- 'Atlassian Cloud account'
2319+
content: |
2320+
{
2321+
"command": "docker",
2322+
"args": ["run", "-i", "--rm", "-e", "CONFLUENCE_URL", "-e", "CONFLUENCE_USERNAME", "-e", "CONFLUENCE_API_TOKEN", "-e", "JIRA_URL", "-e", "JIRA_USERNAME", "-e", "JIRA_API_TOKEN", "ghcr.io/sooperset/mcp-atlassian@sha256:27c8e5b890e16134a443f49683eaa794fdb48ed5bef785c1b4c88a0cd729df56"],
2323+
"env": {
2324+
"CONFLUENCE_URL": "{{CONFLUENCE_URL}}",
2325+
"CONFLUENCE_USERNAME": "{{CONFLUENCE_USERNAME}}",
2326+
"CONFLUENCE_API_TOKEN": "{{CONFLUENCE_API_TOKEN}}",
2327+
"JIRA_URL": "{{JIRA_URL}}",
2328+
"JIRA_USERNAME": "{{JIRA_USERNAME}}",
2329+
"JIRA_API_TOKEN": "{{JIRA_API_TOKEN}}"
2330+
}
2331+
}
2332+
parameters:
2333+
- name: 'Confluence URL'
2334+
key: 'CONFLUENCE_URL'
2335+
placeholder: 'https://your-company.atlassian.net/wiki'
2336+
- name: 'Confluence Username'
2337+
key: 'CONFLUENCE_USERNAME'
2338+
placeholder: '[email protected]'
2339+
- name: 'Confluence API Token'
2340+
key: 'CONFLUENCE_API_TOKEN'
2341+
placeholder: 'your_confluence_api_token'
2342+
- name: 'Jira URL'
2343+
key: 'JIRA_URL'
2344+
placeholder: 'https://your-company.atlassian.net'
2345+
- name: 'Jira Username'
2346+
key: 'JIRA_USERNAME'
2347+
placeholder: '[email protected]'
2348+
- name: 'Jira API Token'
2349+
key: 'JIRA_API_TOKEN'
2350+
placeholder: 'your_jira_api_token'
2351+
- name: 'UVX'
2352+
prerequisites:
2353+
- 'Python and uv'
2354+
content: |
2355+
{
2356+
"command": "uvx",
2357+
"args": ["--from", "mcp-atlassian==0.11.9", "--hash", "sha256:1ba6a171b5299e554d4e0eff98279e74cdc4eb1c12c8e62be924103d9cd38e5e", "mcp-atlassian"],
2358+
"env": {
2359+
"CONFLUENCE_URL": "{{CONFLUENCE_URL}}",
2360+
"CONFLUENCE_USERNAME": "{{CONFLUENCE_USERNAME}}",
2361+
"CONFLUENCE_API_TOKEN": "{{CONFLUENCE_API_TOKEN}}",
2362+
"JIRA_URL": "{{JIRA_URL}}",
2363+
"JIRA_USERNAME": "{{JIRA_USERNAME}}",
2364+
"JIRA_API_TOKEN": "{{JIRA_API_TOKEN}}"
2365+
}
2366+
}
2367+
parameters:
2368+
- name: 'Confluence URL'
2369+
key: 'CONFLUENCE_URL'
2370+
placeholder: 'https://your-company.atlassian.net/wiki'
2371+
- name: 'Confluence Username'
2372+
key: 'CONFLUENCE_USERNAME'
2373+
placeholder: '[email protected]'
2374+
- name: 'Confluence API Token'
2375+
key: 'CONFLUENCE_API_TOKEN'
2376+
placeholder: 'your_confluence_api_token'
2377+
- name: 'Jira URL'
2378+
key: 'JIRA_URL'
2379+
placeholder: 'https://your-company.atlassian.net'
2380+
- name: 'Jira Username'
2381+
key: 'JIRA_USERNAME'
2382+
placeholder: '[email protected]'
2383+
- name: 'Jira API Token'
2384+
key: 'JIRA_API_TOKEN'
2385+
placeholder: 'your_jira_api_token'
2386+
- id: 'clickup'
2387+
name: 'ClickUp'
2388+
description: 'Comprehensive ClickUp MCP server for project management integration with AI through Model Context Protocol. Supports task management, time tracking, workspace organization, document management, member management, and tag operations with 36 available tools for complete ClickUp automation.'
2389+
author: 'taazkareem'
2390+
url: 'https://github.com/TaazKareem/clickup-mcp-server'
2391+
tags:
2392+
- 'clickup'
2393+
- 'project-management'
2394+
- 'task-management'
2395+
- 'time-tracking'
2396+
- 'productivity'
2397+
- 'automation'
2398+
- 'workflow'
2399+
- 'team-collaboration'
2400+
- 'workspace'
2401+
- 'api-integration'
2402+
prerequisites:
2403+
- 'ClickUp account'
2404+
- 'ClickUp API key'
2405+
content:
2406+
- name: 'NPX'
2407+
prerequisites:
2408+
- 'Node.js'
2409+
content: |
2410+
{
2411+
"command": "npx",
2412+
"args": ["-y", "@taazkareem/[email protected]", "--hash", "sha256:yAu9DCsGc8NLwXk3n/JhjjcFfdl+8fv7lcbnVUygRgO8dcG1PFEH/tgcHGpLEtBUx00z13mBH8FiSKUjd4pv5Q=="],
2413+
"env": {
2414+
"CLICKUP_API_KEY": "{{CLICKUP_API_KEY}}",
2415+
"CLICKUP_TEAM_ID": "{{CLICKUP_TEAM_ID}}",
2416+
"DOCUMENT_SUPPORT": "{{DOCUMENT_SUPPORT}}"
2417+
}
2418+
}
2419+
parameters:
2420+
- name: 'ClickUp API Key'
2421+
key: 'CLICKUP_API_KEY'
2422+
placeholder: 'pk_your_clickup_api_key'
2423+
- name: 'ClickUp Team ID'
2424+
key: 'CLICKUP_TEAM_ID'
2425+
placeholder: 'your_team_id'
2426+
- name: 'Document Support'
2427+
key: 'DOCUMENT_SUPPORT'
2428+
placeholder: 'true'
2429+
optional: true

0 commit comments

Comments
 (0)