Submit to Aivyx Hub

Share your MCP server configs and agent templates with the community. All submissions are reviewed before publishing.

1

Fork the Repo

Fork AivyxDev/aivyx-hub on GitHub to your account.

2

Add Your Manifest

Create a JSON file in src/content/mcp-servers/ or src/content/templates/ following the schema below.

3

Test Locally

Run npm run build to validate your schema, then verify with aivyx.

4

Submit a PR

Open a pull request. The Aivyx team will review and merge.

MCP Server Schema

// src/content/mcp-servers/your-server.json
{
  "display_name": "Your Server",
  "description": "Brief description of what this MCP server does",
  "category": "developer",
  "tags": ["relevant", "tags"],
  "icon": "🔧",
  "runtime": "node",
  "command": "npx",
  "args": ["-y", "@scope/mcp-server-name"],
  "env_vars": [
    {
      "name": "API_KEY",
      "required": true,
      "description": "API key for the service"
    }
  ]
}

Agent Template Schema

// src/content/templates/your-agent.json
{
  "display_name": "Your Agent",
  "description": "Brief description of this agent's purpose",
  "category": "general",
  "tags": ["relevant", "tags"],
  "icon": "🤖",
  "capabilities": ["filesystem", "web_search"],
  "mcp_servers": ["github", "filesystem"],
  "mcp_servers_optional": ["memory"],
  "system_prompt": "Your system prompt here.\nBe specific about role, tone, and behavior."
}

Guidelines

  • File naming — Use lowercase with hyphens (my-server.json, not MyServer.json). The filename becomes the install ID.
  • Descriptions — Keep under 100 characters, be specific
  • System prompts — Explain the agent's role, constraints, and tone
  • Tags — Use 2-5 relevant tags for discoverability
  • Icons — Use a single emoji that represents the tool/agent
  • Categories — Choose from: developer, productivity, data, communication, operations, research, creative, support, general
Fork on GitHub Full Contributing Guide