Creating Agents & Tools
You need to be signed in with at least the contributor role. Open the Agents page, switch to the tab for the type you want, and use its New button. Each creation auto-provisions a git repo.
Agents
New agent (/agents/new):
| Field | Required | Notes |
|---|---|---|
| Name | ✓ | e.g. My Awesome Agent. |
| Slug | ✓ | Lowercase, URL-safe; auto-derived from the name. |
| Description | — | What the agent does. |
| Category | — | Healthcare, Education, Agriculture, Finance, Legal, Government, Customer Support, HR, Marketing, Robotics, Other. |
| Pricing | — | Free, Freemium, Paid, or Enterprise. |
| Endpoint URL | — | Where the agent is reachable, e.g. https://api.example.com/agent. |
| Tags | — | Comma-separated, e.g. chat, reasoning, tools. |
Agents are reviewed by a moderator before appearing in public listings. You can also publish under an organization you belong to.
MCP Servers, Workflows & Prompts
These three share one lightweight form and publish immediately (no moderation
queue). Create from /agents/mcp-servers/new, /agents/workflows/new or
/agents/prompts/new. Common fields: Name, Slug, Summary, Tags,
and a Visibility (public/private) toggle, plus a type-specific body:
| Type | Endpoint field | Main content field |
|---|---|---|
| MCP Server | Server URL / Command (e.g. npx -y @scope/server) | Configuration (JSON) — the client config snippet |
| Workflow | — | Steps / Definition — plain steps or a YAML/JSON definition |
| Prompt | — | Prompt Text — the template itself |
After creating
Each item gets a clone panel for its git repo. Push the full definition, config or prompt text there so it's versioned:
git clone <clone-url>
Next: Browsing & Discovery · Import from GitHub · Agents & Tools overview.