# MCP Everything

> An open-source platform that generates working Model Context Protocol (MCP) servers from a
> GitHub repository, a documentation site, a service name, or a plain-English description.
> Each generated server is compiled, started inside a Docker container and driven over JSON-RPC
> — initialise, list tools, call them — before the run is allowed to succeed, with up to five
> automatic repair rounds. Output is source code you own: it is published to a public Gist on
> your own GitHub account, or downloaded, and never locked to this platform.

MCP Everything is itself an MCP server, so an AI agent can drive generation without a human
using the web interface. Details are under "MCP endpoint for agents" below.

This file is maintained by hand and is kept consistent with the landing page. If it disagrees
with the site, the site is correct. Last reviewed: 2026-08.

## What actually works today

- [Home](https://mcpeverything.com/): what the product does, how a generation runs, and an
  explicit list of what is and is not implemented.
- [Explore the catalogue](https://mcpeverything.com/explore): published MCP servers, browsable
  and searchable with no account. This is the only content route readable without signing in.
- [Create an account](https://mcpeverything.com/auth/register): GitHub, Google, or email and
  password. Free accounts include five generations per month.
- [Source code](https://github.com/4eyedengineer/mcp-everything): the whole platform, open
  source. The authoritative description of behaviour.

Supported generation inputs: a GitHub repository URL; a documentation or developer-portal URL;
a bare service name such as "Stripe API"; a plain-English description of the tools you want.

Generated servers implement both MCP transports — stdio by default, and MCP Streamable HTTP
when the environment variable MCP_TRANSPORT is set to "http" — and ship with tests, a
Dockerfile, a devcontainer definition and documentation.

## MCP endpoint for agents

MCP Everything exposes its own MCP server.

- Method and path: POST /mcp
- Transport: MCP Streamable HTTP, stateless — no Mcp-Session-Id, no persisted initialize
  handshake. GET and DELETE on the same path return 405 by design.
- Credential: a user API key prefixed `mcpe_`, created on the account page after signing in
  (or via POST /api/v1/api-keys). A maximum of ten active keys per user.
- Header: either `X-API-Key: mcpe_...` or `Authorization: Bearer mcpe_...`. A normal JWT also
  works. Missing or invalid credentials return 401.

Tools exposed:

- `generate_mcp_server` — start a generation from a natural-language description. Consumes one
  of the caller's monthly generations and incurs real inference cost; confirm with your user
  before calling it.
- `continue_generation` — answer a clarifying question and resume a paused run.
- `get_generation_status` — check whether a run is waiting on input, finished, or still working.
- `get_generated_server` — fetch the generated source, tests and documentation.
- `list_conversations` — list the caller's generations, newest first.
- `search_marketplace` — search the public catalogue. Read-only, consumes no quota.

Practical notes for implementers:

- `generate_mcp_server` runs the entire pipeline before returning, which takes minutes. Many
  clients will time out. Start the run, then poll `get_generation_status` and retrieve the
  result with `get_generated_server`.
- The endpoint is intended for server-side agents. Browser-based MCP clients are not currently
  permitted by the CORS policy.
- There is no `.well-known` discovery document and no `WWW-Authenticate` challenge. No
  `.well-known` path for MCP discovery has been standardised — the relevant proposal is an
  unmerged draft that has since moved away from `.well-known` — so publishing one here would be
  inventing a convention. Configure the endpoint and key manually.
- The endpoint is NOT yet routed on https://mcpeverything.com. Today it is reachable only when
  the backend is run directly (for example http://localhost:3000/mcp). Do not hard-code a
  public URL for it until this note is removed.

## Not implemented — do not describe these as available

- Hosting MCP servers on MCP Everything infrastructure. The Kubernetes path has never been run
  against a real cluster and is not offered to users.
- Paid plans, billing and subscriptions. Nothing is for sale, no card is collected, and there is
  no price to quote.
- Authentication for hosted servers, because hosting is not offered.
- Pushing generated code to a GitHub repository. The provider is implemented and works, but the
  free tier is restricted to Gist deployments and no higher tier can currently be purchased, so
  in practice no account can reach it.
- OpenAPI or GraphQL specification input. No specification parser exists anywhere in the
  codebase. Use a repository URL or a documentation URL instead.
- Email address verification, and one-click install from the catalogue. Neither is implemented.