Skip to content

fiscaltec/claude-marketplace

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 

Repository files navigation

Internal Claude Marketplace

A centralized hub for discovering, sharing, and deploying Claude-powered tools, prompts, MCP servers, and integrations across your organization.

Overview

The Internal Claude Marketplace enables teams to:

  • Share & Discover proven Claude prompts and conversation templates
  • Install & Deploy MCP (Model Context Protocol) servers
  • Distribute custom skills, integrations, and extensions
  • Collaborate on Claude best practices and use cases

Quick Start

For Users

Browse the Marketplace

  1. Navigate to the marketplace interface
  2. Use filters to find prompts, MCP servers, or tools
  3. Preview items and read community reviews
  4. Click "Install" or "Copy" to use

Install an MCP Server

  1. Find the MCP server in the marketplace
  2. Click "Install" and follow the setup wizard
  3. Configure any required API keys or settings
  4. Restart Claude Code to activate the server

Use a Prompt Template

  1. Browse the Prompts section
  2. Click on a template to preview
  3. Copy to clipboard or import directly
  4. Customize parameters for your use case

For Contributors

Submit a New Item

  1. Prepare your submission (see Contribution Guidelines)
  2. Test thoroughly in your environment
  3. Create a pull request or use the submission form
  4. Include documentation and examples
  5. Wait for review and approval

Architecture

System Components

┌─────────────────────────────────────────────┐
│         Marketplace Frontend                │
│  (Browse, Search, Install Interface)        │
└─────────────────┬───────────────────────────┘
                  │
┌─────────────────▼───────────────────────────┐
│         Marketplace Backend                 │
│  - Item Registry                            │
│  - Version Control                          │
│  - Authentication & Authorization           │
│  - Analytics & Usage Tracking               │
└─────────────────┬───────────────────────────┘
                  │
┌─────────────────▼───────────────────────────┐
│         Storage Layer                       │
│  - Item Metadata (Database)                 │
│  - Binary Assets (Object Storage)           │
│  - Documentation (Git Repository)           │
└─────────────────────────────────────────────┘

Item Types

Type Description Format
Prompts Reusable conversation templates Markdown/JSON
MCP Servers Model Context Protocol servers NPM package/Binary
Skills Claude Code custom skills Directory structure
Slash Commands Custom Claude Code commands Markdown files
Integrations Third-party tool connections Various

Installation Guide

Prerequisites

  • Claude Code installed (latest version recommended)
  • Network access to internal marketplace endpoint
  • Authentication credentials for your organization

Installing Marketplace Items

MCP Servers

# Via CLI (if available)
claude-marketplace install mcp-server-name

# Manual installation
1. Download the MCP server package
2. Extract to your MCP servers directory
3. Add configuration to claude_desktop_config.json:
{
  "mcpServers": {
    "server-name": {
      "command": "node",
      "args": ["path/to/server/index.js"],
      "env": {
        "API_KEY": "your-api-key"
      }
    }
  }
}

Prompts & Templates

# Copy to your prompts directory
cp downloaded-prompt.md ~/.claude/prompts/

# Or import directly in Claude Code
/import-prompt path/to/prompt.md

Custom Skills

# Clone to skills directory
git clone internal-repo/skill-name.git ~/.claude/skills/skill-name

# Or use the marketplace installer
claude-marketplace install skill skill-name

Usage Examples

Example 1: Using a Code Review Prompt

# After installing the "Code Review Assistant" prompt:

1. Open Claude Code
2. Reference the prompt: "Use the Code Review Assistant prompt"
3. Provide your code for review
4. Receive structured feedback on:
   - Code quality
   - Security vulnerabilities
   - Performance optimizations
   - Best practices

Example 2: Deploying an MCP Server

# Install the "Internal API Explorer" MCP server
claude-marketplace install mcp-internal-api-explorer

# Configure with your API endpoint
claude-config set mcp-internal-api-explorer.endpoint https://api.internal.com

# Use in Claude Code
# The MCP server now provides context about internal APIs automatically

Example 3: Using a Custom Skill

# Install the "Asana Task Creator" skill
claude-marketplace install skill asana-task-creator

# In Claude Code, invoke the skill
/skill asana-task-creator

# Follow the interactive prompts to create tasks

Contribution Guidelines

Submitting New Items

Quality Standards

  • ✅ Well-documented with clear usage instructions
  • ✅ Tested in production-like environment
  • ✅ Includes examples and use cases
  • ✅ Security reviewed (especially for MCP servers)
  • ✅ No hardcoded credentials or sensitive data
  • ✅ Follows naming conventions: category-name-descriptor

Required Files

For all submissions:

  • README.md - Clear description and usage guide
  • CHANGELOG.md - Version history
  • LICENSE - Internal use license terms
  • metadata.json - Marketplace metadata

Metadata Format

{
  "name": "item-name",
  "version": "1.0.0",
  "type": "mcp-server|prompt|skill|command",
  "author": "Team Name",
  "description": "Brief description",
  "tags": ["tag1", "tag2"],
  "dependencies": [],
  "compatibility": {
    "claudeCode": ">=1.0.0"
  },
  "documentation": "README.md",
  "support": "[email protected]"
}

Submission Process

  1. Prepare Your Submission

    • Create a new branch: git checkout -b marketplace/item-name
    • Add all required files
    • Test installation process
  2. Create Pull Request

    • Use PR template
    • Fill out security checklist
    • Add maintainers as reviewers
  3. Review Process

    • Automated tests run
    • Security scan performed
    • Manual review by marketplace team
    • Feedback or approval within 5 business days
  4. Publication

    • Item appears in marketplace
    • Announcement in #claude-marketplace channel
    • Added to discovery feed

MCP Server Guidelines

  • Must implement standard MCP protocol
  • Include health check endpoint
  • Handle errors gracefully
  • Log to standard locations
  • Document all required environment variables
  • Provide setup script if configuration is complex

Prompt Template Guidelines

  • Use clear parameter placeholders: {variable_name}
  • Include example inputs and outputs
  • Specify Claude model compatibility
  • Document expected response format
  • Provide context on best use cases

Security Requirements

All Submissions Must:

  • Pass automated security scanning
  • Not contain hardcoded secrets
  • Use secure credential management
  • Validate all inputs
  • Handle sensitive data appropriately
  • Include security documentation

MCP Servers Must Also:

  • Implement authentication
  • Use HTTPS for external connections
  • Rate limit API calls
  • Log security events
  • Follow principle of least privilege

Marketplace Categories

Prompts & Templates

  • Code Generation
  • Code Review
  • Documentation
  • Testing
  • Architecture Design
  • Debugging Assistance

MCP Servers

  • Internal APIs
  • Database Connectors
  • Cloud Services
  • CI/CD Integration
  • Monitoring & Observability

Skills

  • Project Management (Asana, Jira)
  • Documentation Generation
  • Code Quality Tools
  • Deployment Automation

Integrations

  • Slack Notifications
  • Email Systems
  • Analytics Platforms
  • Development Tools

Best Practices

For Users

Discovery

  • Star items you find useful
  • Leave reviews to help others
  • Check compatibility before installing
  • Read changelogs for updates

Installation

  • Test in development environment first
  • Back up configuration before changes
  • Follow security guidelines
  • Keep items updated

Usage

  • Report bugs through proper channels
  • Share feedback with authors
  • Document your own use cases
  • Contribute improvements back

For Contributors

Development

  • Follow organization coding standards
  • Write comprehensive tests
  • Document configuration options
  • Version semantically (semver)
  • Maintain backward compatibility when possible

Maintenance

  • Respond to issues promptly
  • Keep dependencies updated
  • Monitor usage analytics
  • Deprecate responsibly with migration guides

Support & Resources

Getting Help

Reporting Issues

Use the issue template:

**Item Name**:
**Version**:
**Issue Type**: Bug | Feature Request | Security
**Description**:
**Steps to Reproduce**:
**Expected Behavior**:
**Actual Behavior**:
**Environment**:

FAQ

Q: Can I submit proprietary tools? A: Yes, all items are internal to the organization.

Q: How do I update an installed item? A: Use claude-marketplace update item-name or check for updates in the UI.

Q: Who reviews submissions? A: The Marketplace Review Team + designated security reviewers for MCP servers.

Q: Can I charge teams for using my items? A: No, the marketplace is for internal collaboration. Cross-charging should be handled through normal budget processes.

Q: What if my item breaks? A: Items can be rolled back to previous versions. Contact support immediately.

Roadmap

Current Focus (Q4 2024)

  • Enhanced search and filtering
  • Automated compatibility testing
  • Usage analytics dashboard
  • Improved submission workflow

Coming Soon

  • Item versioning UI
  • Dependency management
  • A/B testing framework
  • Community ratings and reviews
  • One-click installation for all item types
  • Integration with internal SSO

Governance

Marketplace Team

  • Product Owner: [Name]
  • Technical Lead: [Name]
  • Security Review: [Team Name]
  • Community Manager: [Name]

Policies

Acceptable Use

  • Items must serve legitimate business purposes
  • No malicious code or intentional security vulnerabilities
  • Respect data privacy and compliance requirements
  • Follow company code of conduct

Review Criteria

  1. Technical quality and functionality
  2. Security and compliance
  3. Documentation completeness
  4. User experience
  5. Organizational value

Deprecation Policy

  • 90-day notice for major breaking changes
  • 30-day notice for security-related removals
  • Migration guides required
  • Support during transition period

License

All marketplace items are proprietary to [Company Name] and subject to internal use policies. See individual item licenses for specific terms.

Contributing to the Marketplace Platform

The marketplace platform itself is open for contributions:

git clone internal-repo/claude-marketplace.git
cd claude-marketplace
npm install
npm run dev

See CONTRIBUTING.md for development guidelines.


Version: 1.0.0 Last Updated: 2025-11-10 Maintained by: Claude Marketplace Team

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •