Your Vanity Link

Every mctx server gets a custom vanity link. Use it everywhere you promote your server.

What is a Vanity Link?

Every mctx server gets a custom vanity link:

https://your-slug.mctx.ai

This is your server's home on the web. When someone visits, they see a public info page with everything they need to subscribe.

Your info page shows:

Server name and description
Current pricing (per 1,000 requests)
Available versions
One-click subscribe button
Installation instructions (after subscribing)

Use this link everywhere you promote your server.

Why Vanity Links Matter

Your vanity link is your primary distribution URL. It's:

Memorable - Short, clean, easy to share
Professional - Branded under mctx.ai domain
Conversion-optimized - One-click subscribe flow
Always up-to-date - Pricing, versions, and status sync automatically

Instead of sending developers to a GitHub repo or documentation site, send them to your vanity link. They can subscribe immediately.

How to Use Your Vanity Link

Twitter/X:

Just launched [Server Name] 🚀

[One sentence describing what it does]

Try it: https://your-slug.mctx.ai

#MCP #AI

Discord:

Hey all! Built an MCP server for [use case].

Check it out: https://your-slug.mctx.ai

Happy to answer questions!

Reddit:

I built [Server Name] to solve [problem].

You can try it here: https://your-slug.mctx.ai

Let me know what you think!

Directories

awesome-mcp-servers:

- [Your Server Name](https://your-slug.mctx.ai) - Brief description

MCP.so submission:

Server URL: https://your-slug.mctx.ai

Use your vanity link as the primary URL in all directory submissions. It's the best landing page for new users.

GitHub README

Add your vanity link to your repo's README for easy discovery:

## Try It

Subscribe at [your-slug.mctx.ai](https://your-slug.mctx.ai)

Or create a badge:

[![Subscribe on mctx](https://img.shields.io/badge/Subscribe-mctx-blue)](https://your-slug.mctx.ai)

Developer Blogs and Content

When writing about your server, link to your vanity page:

You can try [Server Name](https://your-slug.mctx.ai) with a one-click subscribe.

Email Signatures

If you engage with communities via email, add your vanity link:

---
Built [Server Name]: https://your-slug.mctx.ai

The Redirect to Marketing Site

When someone visits just the subdomain root (https://your-slug.mctx.ai/), they're redirected to the full server info page:

https://your-slug.mctx.ai/ → https://mctx.ai/servers/your-slug

This keeps the URL short and memorable while providing a full-featured landing page.

Pro tip: Always share https://your-slug.mctx.ai (the short version). It's easier to remember and type.

Version-Specific Links

Your vanity link also supports version-specific pages:

https://your-slug.mctx.ai/v1.0.0

This shows information specific to that version, including:

Version-specific changelog
What changed from previous versions
Installation instructions for that exact version

When to use version-specific links:

Announcing a new major version
Linking to documentation for a specific version
Troubleshooting version-specific issues

Most of the time, use the base vanity link (https://your-slug.mctx.ai). Subscribers can choose their version after subscribing.

Customize Your Server Info

What appears on your vanity link page is controlled by your mctx.json file:

{
  "name": "Your Server Name",
  "description": "Brief description of what your server does",
  "version": "1.0.0"
}

Best practices:

Name - Clear and descriptive (e.g., "Weather API", "SEC Filings Search")
Description - One sentence explaining the value (see Writing Effective Descriptions)
Version - Semantic versioning (major.minor.patch)

Changes to mctx.json are reflected on your info page with the next deployment.

Tracking Visits (Coming Soon)

Note: Visit analytics for vanity links are not yet available. When implemented, you'll be able to see:

How many people viewed your server page
Which promotion channels drove the most traffic
Conversion rate from view to subscribe

For now, track subscriber growth in your dashboard to gauge promotion effectiveness.

Vanity Link Best Practices

Do:

Share it everywhere - Twitter, Discord, Reddit, GitHub, blog posts
Keep your slug short - Easier to remember and type (e.g., weather vs weather-api-v2-production)
Update your description - Keep mctx.json description accurate as your server evolves
Use it as your primary URL - Not a GitHub repo link, not docs, your vanity link

Don't:

Don't link to versioned endpoints - Use the base link (your-slug.mctx.ai), not /v1.0.0
Don't change your slug - It breaks all existing links (slug is permanent)
Don't use generic slugs - my-server or test-server won't work; they're taken

Example Promotion Flow

Here's how a developer might promote their server using the vanity link:

Day 1 - Launch:

Publish to MCP Community Registry
Tweet: "Just launched Weather API on mctx: https://weather-api.mctx.ai"
Post to Discord MCP server: "Built a weather MCP server: https://weather-api.mctx.ai"

Week 1:

Submit to awesome-mcp-servers with link: https://weather-api.mctx.ai
Write blog post on Dev.to, link to: https://weather-api.mctx.ai
Update GitHub README with: "Try it at weather-api.mctx.ai"

Ongoing:

Include in Twitter bio: "Built https://weather-api.mctx.ai"
Add to email signature: "Weather API: https://weather-api.mctx.ai"
Reference in Reddit comments when relevant

Result: One consistent link across all channels. Easy to track, easy to remember, easy to share.

Next Steps

Publish to Registry - Get discovered in the official MCP Community Registry
Directories and Social - Expand your reach
mctx.json Reference - Customize your server info page

See something wrong? Report it or suggest an improvement — your feedback helps make these docs better.

Your Vanity Link

On this page