Publishing Tools

Submit your MCP server to Hive Market and reach AI agent developers.

Prerequisites

1A Hive Market account. Sign up with your email.
2A working MCP server. Your server must implement the Model Context Protocol and be accessible via npm (npx) or a public Git repository.
3A package on npm or GitHub. Users install your server locally via npx -y your-package, so it must be published somewhere accessible.

Submission Form

Go to Publish and fill out the four-step submission form:

Basic Info

Name — a clear, descriptive name (e.g., “Filesystem MCP Server”)
Slug — URL-friendly identifier, auto-generated from the name
Short description — one sentence summary shown in search results
Long description — detailed Markdown description for the tool page
Category — choose one of the 8 marketplace categories
Icon — upload a square icon (recommended 256x256)

Technical Details

npm package — the npm package name (e.g., @modelcontextprotocol/server-filesystem)
Repository URL — link to your GitHub repository
Command — how to run the server (default: npx)
Arguments — any required CLI arguments
Environment variables — list any required env vars (API keys, tokens)

Pricing

Free — open source, no charges
Per-call — charge per API invocation
Monthly — recurring subscription

Publishing is free. You keep 100% of your tool's revenue — set your own price and collect payments directly.

Review & Submit

Preview your listing, confirm all details, and submit. Your tool goes live immediately — no manual approval queue.

Example MCP Server Package

A minimal MCP server npm package should have a binary entry point and list the MCP SDK as a dependency:

package.jsonJSON

{
  "name": "@your-org/mcp-server-example",
  "version": "1.0.0",
  "bin": {
    "mcp-server-example": "./dist/index.js"
  },
  "dependencies": {
    "@modelcontextprotocol/sdk": "^1.0.0"
  }
}

Best Practices

Write a clear description

Explain what your tool does, what capabilities it gives the AI agent, and what use cases it supports. Users search by keyword, so be specific.

Document environment variables

If your server needs API keys or tokens, list them clearly. Tell users where to obtain them and what permissions they need.

Keep the install simple

Aim for a zero-config npx -y your-package install. Minimize required arguments and provide sensible defaults.

Test with multiple clients

Verify your server works with Claude Desktop, Cursor, and Windsurf before publishing. Each client has slight differences in how it handles tool calls.

Ready to publish?

Head to the Publish page to submit your MCP server. If you need help building one, check out the MCP Basics guide first.