MCP server submission checklist: from repository to review
Check source ownership, released artifacts, endpoint access and every selected directory prerequisite before authorizing paid automatic MCP submissions.
Read the guide →Guides
Practical how-tos for publishing an MCP server, each with concrete checks and links to the primary docs.
Prepare server.json and a verifiable MCP registry namespace
Keep registry identity, package metadata, transport, and release versions aligned. Troubleshoot ownership and remote-endpoint mistakes before publishing.
Read the guide →Automate checked MCP submissions with preflight, payment and evidence
Connect owner accounts, validate every destination for free, authorize the exact scope, pay a bound launch through MPP, and track automatic submission results.
Read the guide →How to evaluate an MCP directory before installing a server
A practical discovery workflow for checking publisher identity, transport, permissions, and installation evidence across MCP catalogs.
Read the guide →Prepare an awesome-mcp-servers pull request maintainers can review
Check list scope, Glama evaluation, Markdown formatting, duplicates, and review evidence before contributing an installable MCP server.
Read the guide →Maintain MCP directory listings when your server changes
A release-driven workflow for detecting stale install commands, ownership details, endpoint URLs, and capability descriptions across MCP listings.
Read the guide →Where to start
Preparing a first release? Read the submission checklist. Hit an ownership error? Use the manifest and namespace guide. Choosing software to install? Read the discovery guide first.