marketplace MCP — Use Cases, Install & Live Demo

Why use it

Key features

Security-audited skill inventory
One-click install via CLI
Signed skill manifests (known publisher)
Permission declarations up front
Compatibility badges: Claude, Codex, Claude Code
Update/rollback support

Live Demo

What it looks like in practice

marketplace-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "marketplace-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aiskillstore/marketplace",
        "~/.claude/skills/marketplace"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "marketplace-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aiskillstore/marketplace",
        "~/.claude/skills/marketplace"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "marketplace-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aiskillstore/marketplace",
        "~/.claude/skills/marketplace"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "marketplace-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aiskillstore/marketplace",
        "~/.claude/skills/marketplace"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "marketplace-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aiskillstore/marketplace",
        "~/.claude/skills/marketplace"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "marketplace-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/aiskillstore/marketplace",
          "~/.claude/skills/marketplace"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add marketplace-skill -- git clone https://github.com/aiskillstore/marketplace ~/.claude/skills/marketplace

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use marketplace

How to install a vetted skill instead of a random GitHub repo

👤 Enterprise and regulated users who can't install arbitrary code ⏱ ~10 min beginner

When to use: Your org requires reviewed dependencies and you want skills without going through procurement each time.

Prerequisites

Marketplace installed — git clone https://github.com/aiskillstore/marketplace ~/.claude/skills/marketplace

Flow

Browse catalog

List marketplace skills for GA4/analytics use cases.✓ Copied

→ Catalog subset with audit status + permissions
Inspect permissions

Show me what permissions the 'ga4-setup' skill requests and what it sends externally.✓ Copied

→ Explicit permission + egress disclosure
Install

Install ga4-setup from marketplace.✓ Copied

→ Skill added to ~/.claude/skills with manifest

Outcome: A reviewed skill installed without audit overhead.

Pitfalls

Audit status ages with updates — Check manifest timestamp; re-review if >90 days since last audit

Migrate from random git clones to marketplace equivalents

👤 Teams cleaning up ~/.claude/skills after months of accretion ⏱ ~30 min intermediate

When to use: Your skills folder has 20+ repos, nobody remembers why half of them are installed.

Flow

Inventory

List every skill in ~/.claude/skills and check if a marketplace equivalent exists.✓ Copied

→ Per-skill: keep, migrate, drop
Migrate

Replace matched skills with marketplace versions. Preserve any local config overrides.✓ Copied

→ Backups + fresh installs

Outcome: A reviewable skills folder with known provenance.

Publish your own skill to the marketplace

👤 Skill authors wanting wider distribution with the audit badge ⏱ ~60 min intermediate

When to use: You built a skill and want the credibility of a vetted store listing.

Prerequisites

Working skill with clean SKILL.md — Use claude-code-skill-factory-skill /validate-output first

Flow

Prepare listing

Prepare a marketplace listing for my skill: description, permissions, egress list, screenshots.✓ Copied

→ Listing draft following marketplace conventions
Submit for audit

Open a PR to aiskillstore/marketplace with the listing.✓ Copied

→ PR opened; audit checklist surfaces

Outcome: Skill submitted with a clean audit checklist.

Combine with: claude-code-skill-factory-skill

Combinations

Pair with other MCPs for X10 leverage

marketplace-skill + agent-skills-cli-skill

Use the CLI for install + marketplace for curation

Browse marketplace to find a vetted SEO skill, then install with agent-skills-cli.✓ Copied

marketplace-skill + claude-code-skill-factory-skill

Build with Factory, publish to marketplace

/build my skill with Factory, then publish to marketplace with the publish flow.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
Catalog browse	query?	Finding a vetted skill
Permission inspect	skill_name	Before install
Install	skill_name	After inspection
Migrate	local_path	Cleaning up accretion
Publish	skill_path, listing	Submitting new skills

Cost & Limits

What this costs to run

API quota: None
Tokens per call: 0 at marketplace level; depends on each skill
Monetary: Free
Tip: Prefer marketplace installs over raw clones to cut audit overhead.

Security

Permissions, secrets, blast radius

Credential storage: No credentials at marketplace level

Data egress: Marketplace itself doesn't egress; each listed skill declares its own egress

Audit ≠ zero risk. Still review each skill's declared egress and permissions before enabling for sensitive work.

Troubleshooting

Common errors and fixes

Skill install fails signature check

Update marketplace clone; signing keys may have rotated

Verify: git -C ~/.claude/skills/marketplace pull

A marketplace skill behaves differently from raw upstream

Marketplace sometimes pins older versions for audit stability; check manifest for pinned commit

Alternatives

marketplace vs others

Alternative	When to use it instead	Tradeoff
agent-skills-cli-skill	You want a larger, less-curated catalog	Less audit, more options
awesome-llm-skill	You want community breadth	Quality varies widely

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills