@
feat(web): SEO — server-rendered template pages + /guides articles - templates/[slug] converted from client to server component: per-template generateMetadata (title/description/canonical/OG) + SoftwareApplication JSON-LD; code-audit toggle split into a client island; missing/non-public templates now return a real 404. - sitemap.ts pulls public template slugs live from the API (best-effort) + the new /guides routes. - new /guides section: 3 server-rendered SEO articles (host MCP with OAuth, hosted-platforms comparison, MintMCP alternative) with TechArticle JSON-LD; Guides link added to the marketing nav. - lib/seo.ts: articleJsonLd + templateJsonLd builders. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> @
This commit is contained in:
Marco Sadjadi
@@ -0,0 +1,110 @@
|
||||
import { JsonLd } from '@/components/json-ld';
|
||||
import { articleJsonLd, pageMetadata } from '@/lib/seo';
|
||||
import Link from 'next/link';
|
||||
import { ArticleShell, H2, P, Strong, UL } from '../article-shell';
|
||||
|
||||
const PATH = '/guides/hosted-mcp-platforms-compared';
|
||||
const TITLE =
|
||||
'Hosted MCP platforms compared: Cloudflare, Smithery, Composio & generating your own';
|
||||
const DESCRIPTION =
|
||||
'The MCP hosting landscape splits into four categories — registries, connector platforms, hosting infra, and generators. Here is which one fits which job.';
|
||||
|
||||
export const metadata = pageMetadata({ title: TITLE, description: DESCRIPTION, path: PATH });
|
||||
|
||||
export default function Page() {
|
||||
return (
|
||||
<>
|
||||
<JsonLd
|
||||
data={articleJsonLd({
|
||||
title: TITLE,
|
||||
description: DESCRIPTION,
|
||||
path: PATH,
|
||||
datePublished: '2026-05-31',
|
||||
})}
|
||||
/>
|
||||
<ArticleShell
|
||||
title={TITLE}
|
||||
subtitle="There are 14,000+ MCP servers out there and a dozen platforms claiming to host them. They are not competing for the same job. Sort them into four buckets and the choice gets obvious."
|
||||
updated="May 2026"
|
||||
>
|
||||
<H2>1. Registries & directories</H2>
|
||||
<P>
|
||||
<Strong>Smithery</Strong>, <Strong>Glama</Strong> and <Strong>PulseMCP</Strong> are about{' '}
|
||||
<em>discovery</em> — finding and listing existing servers (Glama indexes thousands). Some
|
||||
add light hosting on top, but the core value is the catalog and the traffic. Use them to
|
||||
publish a server people can find, or to find one that already does what you need.
|
||||
</P>
|
||||
|
||||
<H2>2. Connector platforms</H2>
|
||||
<P>
|
||||
<Strong>Composio</Strong>, <Strong>Nango</Strong>, <Strong>Klavis</Strong>,{' '}
|
||||
<Strong>Zapier</Strong> and <Strong>Pipedream</Strong> expose <em>their</em> catalog of
|
||||
hundreds of pre-built SaaS integrations as MCP, with managed auth. If your need is
|
||||
"let my agent touch Gmail / Slack / Salesforce," these are the fastest path —
|
||||
you're buying breadth of pre-built connectors, not building your own logic.
|
||||
</P>
|
||||
|
||||
<H2>3. Hosting infrastructure</H2>
|
||||
<P>
|
||||
<Strong>Cloudflare Workers</Strong> is the default for hosting a remote MCP server in
|
||||
production — edge-global, with an OAuth provider library. <Strong>Vercel</Strong>,{' '}
|
||||
<Strong>Render</Strong> and <Strong>Cloud Run</Strong> host custom Node containers too.{' '}
|
||||
<Strong>MintMCP</Strong> sits slightly higher up: one-click wrap of an existing STDIO
|
||||
server into a remote one with auto-OAuth, and it leads on compliance (SOC 2 Type II,
|
||||
GDPR/HIPAA-formatted audit logs). All of these assume <Strong>you bring the code.</Strong>
|
||||
</P>
|
||||
|
||||
<H2>4. Generators (the gap most lists miss)</H2>
|
||||
<P>
|
||||
The first three categories all assume you already have a server, or that a pre-built
|
||||
connector covers your case. Neither is true when you need a <em>bespoke</em> tool — a
|
||||
wrapper around your own internal API, a niche workflow, a one-off integration nobody has
|
||||
built. That's the generator category: describe the tool, get a custom MCP server hosted
|
||||
for you. It's the youngest and least crowded slice, and it's where{' '}
|
||||
<Strong>BuildMyMCPServer</Strong> plays.
|
||||
</P>
|
||||
|
||||
<H2>So which do you pick?</H2>
|
||||
<UL>
|
||||
<li>
|
||||
<Strong>Need a popular SaaS connector?</Strong> A connector platform (Composio / Klavis /
|
||||
Zapier) — don't rebuild what they maintain.
|
||||
</li>
|
||||
<li>
|
||||
<Strong>Have a server and engineers?</Strong> Host it on Cloudflare Workers; wrap your
|
||||
own OAuth or use MintMCP if you want the compliance posture done for you.
|
||||
</li>
|
||||
<li>
|
||||
<Strong>Just browsing for something that exists?</Strong> Smithery or Glama.
|
||||
</li>
|
||||
<li>
|
||||
<Strong>Need a custom tool and don't want to write or host a server?</Strong> A generator
|
||||
— describe it, ship it. Export the source later if you outgrow it.
|
||||
</li>
|
||||
</UL>
|
||||
|
||||
<H2>Where BuildMyMCPServer fits honestly</H2>
|
||||
<P>
|
||||
We're not trying to out-scale Cloudflare's edge or out-catalog Composio. The job we do is
|
||||
the bespoke one: <Strong>prompt → a hosted, OAuth-protected MCP server</Strong>, with
|
||||
install snippets for Claude, Cursor and ChatGPT, an EU/US data-residency choice for teams
|
||||
that care, full TypeScript source export, and a template marketplace to fork from. If your
|
||||
tool is custom and your time is the constraint, that's the wedge. If you need a vetted
|
||||
enterprise SOC 2 host for an existing server today, MintMCP or your own Cloudflare setup is
|
||||
the more honest answer.
|
||||
</P>
|
||||
|
||||
<P>
|
||||
Next:{' '}
|
||||
<Link
|
||||
href="/guides/host-mcp-server-with-oauth"
|
||||
className="text-[--color-accent] hover:underline"
|
||||
>
|
||||
what hosting a remote MCP server with OAuth actually involves
|
||||
</Link>
|
||||
.
|
||||
</P>
|
||||
</ArticleShell>
|
||||
</>
|
||||
);
|
||||
}
|
||||
Reference in New Issue
Block a user