Developer tools + a community to discover your work

Build and publish your MCP. Discover what’s next.

Build, test, and deploy with Dev Studio. Turn APIs, documents, and skills into MCP experiences, publish to the marketplace, and optionally monetize. Explore our directory to find tools for your next project—and help users find yours.

From your first tool to your next user: development tools, publishing, and discovery in one place. Your platform API key connects supported marketplace subscriptions—not arbitrary crawled servers.

Develop · Test · Publish · Get discovered

Bring your work to MCP. Start your way.

Go from an idea to tools people can use. Develop in Dev Studio, connect a REST API, or turn skills and documents into MCP resources. Test and review your work, then publish. Our directory helps people find tools and creators reach users.

From our editor

Your code → custom MCP tools

Start from a template in Dev Studio. Edit code, configure tools, test calls, and deploy before reviewing and publishing your listing.

Open Dev Studio

From a REST API

Your API → MCP tools

Bring an OpenAPI or Swagger spec. Turn your existing API operations into tools an MCP client can call.

Connect a REST API

From skills

Your know-how → reusable instructions

Publish a Markdown skill. Eligible public/free skills can be selected and served through our Skills over MCP endpoint—not executed as code.

Publish a skill

From documents

Your content → searchable knowledge

Upload documents and create an MCP knowledge source. Let AI clients search and retrieve relevant content through the platform.

Upload documents

For creators & providers

Publish it. Put a business behind it.

Offer your MCP for free or choose a paid plan. Platform listings bring discovery, subscriber access, usage tracking, and billing together.

  • Free access
  • Monthly subscriptions
  • Usage-based billing

Paid listings require billing setup and Stripe Connect for payouts. Skills over MCP currently serves eligible public/free skill content only.

Already built an MCP?

Bring your link. Reach the community.

Add your MCP endpoint or import a GitHub source in the listing flow. We attempt tool discovery; you review the result and publish when it’s ready.

  1. Add your source and connection details
  2. Discover tools and review your draft
  3. Publish for users to discover and subscribe
Submit your MCP link

Sign in and submit a source you’re authorized to publish. A repository link may need hosting or connection setup before its tools can be used.

One platform key. Clear access boundaries. Use your platform API key for supported marketplace subscriptions and the separate Skills over MCP endpoint. Crawled directory links alone do not grant platform-key access; provider authentication may still be required.

Set up Skills over MCP

Skills over MCP

One connection. Your selected skills.

Select up to 20 public/free skill Markdown docs and load them in your AI client through a platform MCP endpoint, using your platform API key.

Your AI client follows the instructions. This endpoint serves docs, not scripts or model calls, and does not grant access to crawled MCP servers.

Set up Skills over MCPSign in to configure your selection.

Included, with clear limits

10,000 tool-call attempts
Per account per calendar month (UTC).
60 authenticated requests
Per account per fixed minute, shared across keys. A lower per-key limit still applies.

No document credits. No overage charges.

Interactive Demo

See it in action

Explore every feature with mock data. No sign-up required.

mcpchannel.ai/listings
DEMO

Ready to try the real thing?

REST → MCP

Already have a REST API?

Turn your OpenAPI spec into tools for Claude, Cursor and other MCP clients. Preview the schemas, configure authentication, and publish when you’re ready. Your API stays yours.

Your API. A new interface.

Illustrative integration

01 / Define

Your existing API

A curated OpenAPI specification.

openapi.json

  • GET/users
  • GET/users/{id}
  • GET/orders

Keep your endpoints and business logic.

02 / Configure

MCP Channel

The gateway between API and agent.

  • Tool definitions

    Names and input schemas from your spec.

  • Access & authentication

    Platform-key access and configured provider auth.

  • Request translation

    Tool arguments become HTTP requests.

Review configuration before publishing.

03 / Connect

Tools for your client

Claude, Cursor & compatible MCP clients.

  • list_users

    limit?: number

  • get_user

    id: string

  • list_orders

    status?: string

Published tools appear as slug/toolName.

Animated above: spec → tool definitions

At call time: MCP client → gateway → your API → result

After publication, users enable access and create their platform key on the website. The spec defines the tools; provider credentials still need configuration.

One operation, one tool

Every path × method becomes a named MCP tool. operationId, summary, and parameter schemas carry through.

Authentication, configured once

Review your API’s auth requirements and configure supported provider credentials. The gateway attaches them when translating tool calls.

$ref & requestBody resolved

Nested schemas are dereferenced. JSON and form-urlencoded bodies just work. No manual rewriting.

Free to start

Have documents, not an API?

Upload them. We register an MCP on the marketplace. Others subscribe and ask through the same gateway — one key, no extra URL. Free to start.

You upload

API docs, runbooks, a contract. We index the text.

We list it

A published MCP with ask and list_documents. It shows on Browse.

They call us

Subscribe, paste the gateway into Cursor, ask slug/ask. That is the whole path.

How others call it

  1. 1. Subscribe on /listings/your-docs
  2. 2. Create one mcp_… key — same key as every other listing
  3. 3. Point Cursor at this gateway. Tools: your-docs/ask, your-docs/list_documents
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://www.mcpchannel.ai/api/mcp",
      "headers": {
        "X-MCP-Market-Key": "mcp_YOUR_KEY_HERE"
      }
    }
  }
}
Free to start

Build your MCP in the browser

Write TypeScript or Python. Test instantly. Deploy with one click. Your first project is free — no credit card required.

1

Pick a template

Choose TypeScript or Python. Start from a template or blank.

2

Write code

Monaco editor with syntax highlighting, autocomplete, and AI assist.

3

Test for free

Run any tool in an isolated sandbox. No charge.

4

Deploy

Test deploy (free, 1hr) or production deploy (Pro plan).

Free — 1 project, test deployPro $25/mo — unlimited projects, production deploy

Why mcpchannel.ai

Find MCPs, publish yours, and ship one with our tools. One gateway, one key.

1 key

All subscribed MCPs

Free & Pro

Per-MCP pricing

Secure proxy

Metered & rate-limited

Publish & earn

Stripe Connect payouts

MCPs & Agents

Subscribe to MCP tools and run agents from one place. One API key, one gateway—use in Cursor, Claude, or any MCP client.

REST → MCP

Have a REST API? Paste your OpenAPI spec—we turn it into MCP tools. No backend changes. Your API works as another MCP.

Documents → MCP

Have files, not an API? Upload them. We register a listing; subscribers ask through the gateway with the same key.

Dev Studio

No server yet? Write TypeScript or Python in the browser, test in a sandbox, and publish. First project is free.

Flexible payments

Free or Pro per listing. We take 5% of subscription revenue (popular API marketplaces take 20–25%). Flat fee, metered usage, or both.

Easy subscription & billing

Manage all subscriptions in one dashboard. Create API keys, see usage, and handle billing with Stripe—customer portal and payouts built in.

Playground

Try tools and agents in the browser. Natural language becomes tool calls. Use a test key before you subscribe—no commitment.

LLM evaluation score

We score listings with our LLM so you see quality at a glance. Know what you're getting before you subscribe.

More

Test key try-it

Try before you subscribe

MCP config + guides

Copy config for Cursor, Claude

OAuth & stdio

Connect OAuth; we run stdio MCPs

Reviews & uptime

Ratings and health checks

Convert to MCP

Download spec, self-host if you want

For developers

Discover MCP servers, AI skills, and CLI tools. Subscribe and call them through a single gateway and one API key.

Discover & search

Browse MCPs by category. See tools, README (from GitHub or uploaded), docs and video links, pricing, and reviews before you subscribe.

One API key

Subscribe to as many tools as you want. A single key unlocks all of them in Cursor, Claude, or any MCP client. No per-tool config.

Secure gateway

Every call goes through our gateway. We validate your key, check quotas and rate limits, proxy to the provider, and meter usage.

Usage & billing

Dashboard shows usage this month, quotas, and recent tool calls. Free and Pro plans per MCP. Stripe subscriptions and customer portal.

Playground & MCP mode

Try tools in the browser. Open MCP mode for chat: natural language becomes tool calls. App selector picks which key to use; copy MCP config and install guides for Cursor, Claude, and more.

REST APIs as MCPs

Listings can be backed by a REST API: paste an OpenAPI spec and we turn it into MCP tools. No backend changes. Use a provider test key to try before you subscribe.

Reviews & uptime

See ratings and reviews from other users. We run health checks and show uptime %. Verified badge for vetted MCPs.

Already have paying customers?

Keep your plans. Add an agent.

Your customers already pay you. List your API here and they reach it from Claude, Cursor or any MCP client — on their own key, on their existing plan, billed by you exactly as they are today.

You ask for one thing

Add a field to your listing: “Your API key”. Your subscriber fills it in once, on their dashboard.

Never as a tool argument — so it never lands in an agent’s transcript, and you never see anyone else’s.

You get it on every call

X-MCP-Market-Config:
  {"api_key": "ak_live_..."}

Read one header. That is the whole integration — no accounts to create, no plan logic, no webhooks. Your rate limits and tiers apply unchanged, because it is their key.

Selling to people who don’t have an account yet? List one plan per tier and we handle the subscription — we tell you who signed up, and when they leave.

Publish your MCP — we give you the tools

Already have a server? List it. If not, use Dev Studio, REST → MCP, or documents. We handle discovery, keys, metering, and billing. Free or Pro — payouts via Stripe Connect.

  • Dev Studio: write TypeScript or Python in the browser, test in a sandbox, deploy. First project is free.
  • REST → MCP: paste an OpenAPI spec (or URL); we generate tools and proxy requests—no backend changes. Provide a test key so consumers can try in the Playground.
  • Documents → MCP: upload files; we register a listing. Subscribers ask through the gateway with the same key — no extra URL.
  • HTTP or stdio: provide an MCP URL or paste stdio config—we run stdio MCPs for you.
  • OAuth: require consumers to connect with their Client ID/Secret; we send their token when proxying.
  • GitHub repo README or upload your own; add docs and video links.
  • Tool validation and optional schema checks before proxying.
  • Dashboard: usage per MCP, recent calls, payout history.

Provider dashboard

ListingsCreate, edit, draft/publish
UsagePer-MCP and per-listing
PayoutsStripe Connect, revenue share
IntrospectionTools, prompts, resources

How it works

Three steps to start using MCP servers, skills, and CLI tools.

1

Discover tools

Browse MCP servers, AI skills, and CLI tools. Read docs, check reviews, and subscribe (free or Pro) with one click.

2

One API key

Create an API key in your dashboard. One key works for every MCP you’re subscribed to.

3

Use in your IDE

Add our gateway URL and your key to Cursor or any MCP-compatible client. All tools appear as slug/toolName.

Ready to monetize your MCP?

List your MCP, set your price, and start earning. Consumers get 9127+ tools through one key.