Contribute a template

Eden is an MCP server. MCP is an open protocol, so this endpoint works with any client that speaks it, not one company's:

Most clients take that URL in their settings or config file, as a streamable HTTP server. If yours has a command line, it usually looks like this:

The first connection opens a GitHub sign-in. It establishes who you are so a submission carries your name, and that is all: Eden asks for no write permission, never pushes to your repositories, and never reads private ones.

There are no commands to remember after that. Tell it you want to contribute a template and give it the repo URL. It reads the repo, proposes the title, category and description, asks you only for what the code cannot tell it, and shows you the finished entry before anything is submitted.

You confirm, and if the check passes cleanly it is live right then. No queue and nobody to wait for. If something needs a person, it says what and a maintainer looks. Nothing of yours is copied into Eden: the entry points at your repository, which is also what the Deploy button clones.

Eden's Deploy button clones your repo into a stranger's Vercel account, so a listing is an endorsement. Every submission is checked, and the check is not a formality. Your repo needs to be:

• Public. A Deploy button cannot clone what nobody can see.
• A real Eve agent. It declares eve at a version that exists on npm, calls defineAgent, and has instructions.
• An agent, not a prompt. At least one tool, skill, channel, schedule, subagent or connection. A single model call wrapped in a repo is not a template.
• Runnable by a reviewer. One line they can actually run to see it work. This is the field that gets a template listed or bounced.

Refused outright, because a template is code other people run:

• Install-time scripts (postinstall and its siblings), which run on the machine of whoever clones you.
• Dependencies that do not come from the npm registry, which nobody can review.
• Shelling out, eval, and code assembled at runtime.
• Reading the whole environment at once, which is the shape of a secret leaving.
• Long encoded blobs, which hide what the code does.

Other things are flagged rather than refused, and a maintainer reads them on the pull request: base64 decoded at runtime, direct filesystem access, a missing license, an eve pin far behind current, and every external host your agent talks to.

None of this is a guarantee. It reads your source as text, so it raises the cost of the obvious attempt and hands a person a short list to look at. A human still decides whether it gets listed.

Your template gets a page on Eden that names you, links to your profile and your repository, and carries a Deploy button pointing at your repo. It also becomes installable from the terminal by anyone, because Eden publishes its catalog as an eve registry:

Eden re-runs its check on every listed template daily. If yours falls behind eve, the page says so rather than offering a Deploy button that no longer works. If a listed repository stops passing the safety screen, it comes off the site the same day. Keeping your repo current keeps it listed.

Open the concierge on the home page and describe what you want the agent to do. It will walk you through building it with Eve, one file at a time. Come back here when it runs.