AgenticMarket — Build and Install MCP Servers in One Command

The CLI for Model Context Protocol servers. Create production-ready MCP servers from scratch, or install existing ones into every IDE — no JSON editing, no manual configuration.

---

TL;DR

Build a new MCP server:

npm install -g agenticmarket
agenticmarket create my-weather-server
cd my-weather-server && npm install && npm run dev

Install an existing MCP server:

agenticmarket auth <your-api-key>
agenticmarket install username/server-name

Install an agent skill:

agenticmarket skill list
agenticmarket skill install nextjs-app-router
agenticmarket skill install nextjs-app-router --agent andromity --scope project
agenticmarket skill install nextjs-app-router --agent cursor,claude-code
agenticmarket skill install nextjs-app-router --all --scope user
agenticmarket skill update nextjs-app-router --agent cursor
agenticmarket skill remove nextjs-app-router --agent cursor

Skills are free, public SKILL.md instruction packages. Skill installation does not require an API key. Without --agent or --all, the CLI opens a multi-select prompt so you can choose exactly which agent(s) receive the skill. The CLI writes the native file format for each selected agent, preserves existing files unless --overwrite is supplied, and records a best-effort install event for marketplace analytics. Use --agent or --all in scripts and CI.

create scaffolds a production-ready Hono + TypeScript MCP server with security middleware, rate limiting, and deployment config in ~30 seconds.

install writes MCP entries into VS Code, Cursor, Claude Desktop, and every other IDE you have — automatically.

Browse MCP servers →
Get your API key →
Publish your MCP server and earn →

---

Contents

• What Is AgenticMarket
• Requirements
• Installation
• Quick Start
• Commands
  • create — scaffold a new MCP server
  • auth / install / remove / list / balance / whoami
• Supported IDEs
• How It Works
• For MCP Server Creators
• Project Structure
• Contributing
• FAQ
• License

---

What Is AgenticMarket

AgenticMarket is where developers build and install MCP servers in one command and creators earn on every call.

The Model Context Protocol (MCP) is the open standard that lets AI assistants — in VS Code, Cursor, Claude Desktop, and other tools — call external tools and data sources. AgenticMarket is the distribution and monetization layer built on top of it.

For developers using MCP servers:
One command installs any server into every IDE you have. No hunting for JSON config paths. No manual authentication setup. AgenticMarket distribution and calls are free; external services may still require their own credentials.

For developers publishing MCP servers:
Submit your HTTP MCP server to AgenticMarket for free distribution, health checks, and install analytics. No listing fee, platform fee, or per-call charge.

---

Requirements

• Node.js 20.6 or higher
• For install commands: at least one supported IDE and an AgenticMarket API key
• For create: no account required

---

Installation

Install globally via npm:

npm install -g agenticmarket

Or run without installing via npx:

npx agenticmarket <command>

The shorthand alias amkt is available after global install:

amkt install username/server-name

---

Quick Start

# Step 1 — Authenticate with your API key
agenticmarket auth am_live_xxxx

# Step 2 — Install an MCP server
agenticmarket install agenticmarket/web-reader

# Step 3 — Open your AI assistant
# The tool is ready. No restart required in most IDEs.

The CLI detects every IDE installed on your machine and writes the correct configuration automatically. If you are running the command from inside VS Code or Cursor, those entries appear pre-selected at the top of the prompt.

---

Commands

create

Scaffold a new MCP server project with security middleware, rate limiting, and deployment config.

agenticmarket create <project-name>
agenticmarket create my-weather-api

Option A: Fresh Server (Start from scratch)

Option B: API Wrapper (Turn an existing REST API into an MCP server)

Interactive prompts ask for:

| Prompt | Options | |--------|---------| | Template | Fresh server (blank) or API wrapper (REST API → MCP bridge) | | Deploy target | Cloudflare Workers, Docker (Railway/Render), or None | | Secret auth | Auto-generates MCP_SECRET in .env | | API config (wrapper only) | Base URL, auth type, auth header |

What you get:

my-weather-api/
├── src/
│   ├── index.ts              # Hono server + MCP transport
│   ├── middleware/
│   │   ├── security.ts       # HTTPS, secret header, CORS, header stripping
│   │   └── rateLimit.ts      # Per-IP sliding window (100 req/min)
│   ├── tools/
│   │   ├── index.ts          # Tool registry
│   │   └── echo.ts           # Reference tool (Zod validated)
│   └── types.ts
├── .mcp/server.json          # Official MCP registry schema
├── .env                      # Auto-generated secret
├── .env.example
├── package.json              # dev, build, inspect, validate, release scripts
├── tsconfig.json
├── wrangler.toml             # or Dockerfile, depending on deploy target
└── README.md

Security layers ship enabled by default and are imported as middleware — difficult to accidentally remove:

• Secret header validation (timing-safe constant-time comparison)
• HTTPS enforcement in production (hard reject on HTTP)
• Per-IP rate limiting with Retry-After headers
• CORS (no origins by default)
• X-Powered-By / Server header stripping
• Production requires MCP_SECRET (500 if missing)
• CSP headers + X-Frame-Options DENY
• Body size limit (1 MB — prevents memory DoS)
• Session idle timeout (30 min auto-cleanup)
• Graceful shutdown on SIGTERM/SIGINT

After scaffolding:

cd my-weather-api
npm install
npm run dev        # server at http://localhost:3000
npm run inspect    # MCP Inspector UI at localhost:6274

→ Full create documentation — security details, architecture, roadmap

---

auth

Save and verify your API key locally.

agenticmarket auth <api-key>

Your key is stored in ~/.agenticmarket/config.json. It is never transmitted anywhere except the AgenticMarket platform to authenticate your requests.

---

install

Install an MCP server into your IDE configuration files.

agenticmarket install <username>/<server-name>

# The @ prefix is optional — both are equivalent
agenticmarket install @alice/summarizer
agenticmarket install alice/summarizer

The CLI will:

1. Verify the server exists on AgenticMarket
2. Detect every IDE installed on your machine
3. Present a selection prompt — your active IDE's options appear first
4. Write the MCP configuration entry for each selected target, creating config directories if they do not exist

Smart pre-selection — if you run the command from inside VS Code, Cursor, Windsurf, or Gemini CLI, that IDE's project and global options are pre-ticked.

Name conflict resolution — if a server with the same name is already installed from a different author, you are prompted to assign an alias so both coexist without overwriting each other.

---

remove

Remove an MCP server from all IDE configurations it was installed to.

agenticmarket remove <server-name>

---

list

Show all AgenticMarket MCP servers currently installed across your IDEs.

agenticmarket list

---

balance

Check your current credit balance.

agenticmarket balance

---

whoami

Display your current account details.

agenticmarket whoami

---

Supported IDEs

The CLI automatically detects which IDEs are installed on your machine by checking well-known configuration paths. Only IDEs that are actually present on your system appear in the selection menu.

If an IDE does not appear in the prompt, it is not installed or has not been opened at least once to initialise its config directory.

Detection and Scope

Each IDE supports one or both of:

• Project — configuration lives inside your project folder (e.g. .cursor/mcp.json). Can be committed with your project and shared with your team.
• Global — configuration lives in your home or app-data directory. Available across all projects.

| IDE | Project Config | Global Config | Detection Signal | |---|---|---|---| | VS Code | .vscode/mcp.json | See paths below | VS Code user-data dir exists | | Cursor | .cursor/mcp.json | ~/.cursor/mcp.json | ~/.cursor dir exists | | Claude Desktop | — | See paths below | App config dir exists | | Claude Code | .mcp.json | ~/.claude.json | ~/.claude dir exists | | Windsurf | — | ~/.codeium/windsurf/mcp_config.json | ~/.codeium/windsurf dir exists | | Gemini CLI | .gemini/settings.json | ~/.gemini/settings.json | ~/.gemini dir exists | | Zed | — | See paths below | Zed config dir exists | | Cline (VS Code ext) | — | VS Code globalStorage | Extension settings dir exists | | Codex | — | ~/.codex/config.json | ~/.codex dir exists | | Antigravity | .gemini/antigravity/mcp_config.json | ~/.gemini/antigravity/mcp_config.json | ~/.gemini/antigravity dir exists |

Platform-Specific Global Paths

| IDE | Windows | macOS | Linux | |---|---|---|---| | VS Code | %APPDATA%\Code\User\mcp.json | ~/Library/Application Support/Code/User/mcp.json | ~/.config/Code/User/mcp.json | | Claude Desktop | %APPDATA%\Claude\claude_desktop_config.json | ~/Library/Application Support/Claude/claude_desktop_config.json | ~/.config/claude/claude_desktop_config.json | | Zed | %APPDATA%\Zed\settings.json | ~/Library/Application Support/Zed/settings.json | ~/.config/zed/settings.json |

---

How It Works

Your AI assistant calls a tool
  → AgenticMarket authenticates your API key
  → Your credit balance is verified
  → The request is forwarded to the creator's MCP server
  → The result is returned to your AI assistant
  → Credits are deducted only on a successful response

Charges apply per successful tool call only. If the server is unreachable or returns an error, you are not charged.

The CLI writes MCP server entries using just the plain server name as the key (e.g. web-reader, not agenticmarket/web-reader). This ensures compatibility across all MCP clients — slashes in server names cause parsing issues in several IDEs.

---

For MCP Server Creators

If you have built an MCP server and want it to earn revenue, AgenticMarket handles the distribution, authentication, billing, and payouts.

What you need:

• A publicly accessible HTTPS endpoint serving the MCP protocol
• An AgenticMarket account

How publishing works:

1. Submit your server at [agenticmarket.dev/dashboard/submit](http