Submit Your Asset

Expand the context layer. We index production-ready Model Context Protocol servers, client integrations, and custom prompts to help developers worldwide. Submissions are open-source and completed via pull requests.

Submission Process

  1. Fork & Clone: Fork the public MCP Directory repository on GitHub.
  2. Create Markdown: Create a new markdown file inside `src/content/servers/[your-server-slug].md` with the required parameters in its frontmatter.
  3. Validate & Build: Ensure your markdown compiles successfully. Run `npm run build` locally to prevent verification errors.
  4. Open Pull Request: Submit your PR. Our team will review the code capabilities and verify the execution snippets before merging.

Frontmatter Template Schema

Copy and fill this block inside your `.md` server file:

---
name: "Server Name"
slug: "clean-hyphenated-slug-id"
tagline: "Short 60-character tagline summarizing features."
description: "Detailed description explaining capabilities and resources."
category: "databases" # databases, dev-tools, apis-services, communication, filesystem, browser-automation
tags: ["postgres", "analytics", "sql"]
type: "Community" # Official, Community, Example, Client, Skill
requiresAuth: true
authType: "OAuth"
runtime: "Node.js"
capabilities: ["Dynamic query execution", "JSON schema read"]
useCases: ["Business intelligence logs", "Automated code reviewers"]
installSnippet: "npx -y @modelcontextprotocol/new-server"
securityNotes: "Limit database scopes and verify tokens."
officialUrl: "https://yourwebsite.com"
githubUrl: "https://github.com/your-username/your-repo"
docsUrl: "https://docs.yourwebsite.com"
featured: false
official: false
popularity: 1
lastVerified: "2026-06-15"
---
          

// SUBMISSION RULES

  • No proprietary web wrappers: The adapter must fulfill a specific protocol need. Generic wrappers with no security controls will be rejected.
  • Working Install Snippet: The `installSnippet` must be fully executable over public npx, npm, or pip networks.
  • Responsible Security Docs: Document potential security caveats (like write privileges) clearly in the `securityNotes` block.
  • Appropriate Tags: Categorize accurately to keep active filtering chips working properly.