cba45402ce
- /docs subpages canonicalized to /docs and had no descriptions; each now uses pageMetadata with its own path (was: Google could index at most one) - llms.txt claimed Team EUR 149, RBAC/SLA and BYO-cloud that do not exist; regenerated from lib/seo.ts truth + new llms-full.txt with docs content - sitemap stamped lastModified=now on every request; now real per-route dates from new lib/articles.ts registry (single source for guides index/sitemap/RSS) - new /feed.xml RSS 2.0 route + alternates link in root layout - articleJsonLd: image (per-guide opengraph-image via lib/og-article.tsx), Person author, wordCount; new breadcrumbJsonLd on guides + docs - GSC verification via NEXT_PUBLIC_GSC_VERIFICATION (documented in .env.example) - dropped fabricated Enterprise EUR 499 offer from SoftwareApplication JSON-LD - article-shell: OL/Table/Note primitives for upcoming articles Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SXUwmPVRTD8AKQtio6gCN5
101 lines
3.5 KiB
XML
101 lines
3.5 KiB
XML
import {
|
|
DocsTitle,
|
|
DocsLead,
|
|
DocsH2,
|
|
DocsP,
|
|
DocsList,
|
|
DocsLi,
|
|
DocsCode,
|
|
Mono,
|
|
} from '@/components/docs-page';
|
|
import { JsonLd } from '@/components/json-ld';
|
|
import { breadcrumbJsonLd, pageMetadata } from '@/lib/seo';
|
|
|
|
export const metadata = pageMetadata({
|
|
title: 'MCP concepts',
|
|
description:
|
|
'What Model Context Protocol is: tools, resources and prompts, the Streamable HTTP transport, and how a client discovers and calls a server.',
|
|
path: '/docs/concepts',
|
|
});
|
|
|
|
export default function Concepts() {
|
|
return (
|
|
<>
|
|
<JsonLd
|
|
data={breadcrumbJsonLd([
|
|
{ name: 'Home', path: '/' },
|
|
{ name: 'Docs', path: '/docs' },
|
|
{ name: 'MCP concepts', path: '/docs/concepts' },
|
|
])}
|
|
/>
|
|
<DocsTitle kicker="Get started">MCP concepts</DocsTitle>
|
|
<DocsLead>
|
|
Model Context Protocol is an open standard from Anthropic for connecting AI assistants to
|
|
external tools, data, and APIs. Three primitives, one transport.
|
|
</DocsLead>
|
|
|
|
<DocsH2 id="primitives">The three primitives</DocsH2>
|
|
<DocsList>
|
|
<DocsLi>
|
|
<strong className="text-[--color-fg]">Tools</strong> — functions the AI can invoke.
|
|
Each has a name, a description, an input schema (JSON Schema or Zod), and a server-side
|
|
implementation. The AI decides when to call them based on the description.
|
|
</DocsLi>
|
|
<DocsLi>
|
|
<strong className="text-[--color-fg]">Resources</strong> — read-only data the AI can
|
|
fetch. URI-addressed. Think files, documents, database records.
|
|
</DocsLi>
|
|
<DocsLi>
|
|
<strong className="text-[--color-fg]">Prompts</strong> — parameterized prompt templates
|
|
the server exposes to the client. Used for orchestration patterns the server author
|
|
wants to encourage.
|
|
</DocsLi>
|
|
</DocsList>
|
|
|
|
<DocsH2 id="transport">Transport: Streamable HTTP</DocsH2>
|
|
<DocsP>
|
|
Every generated server speaks <Mono>Streamable HTTP</Mono> (MCP spec 2025-11-25). The
|
|
previous SSE transport was deprecated in June 2025 and is not supported here. One HTTP
|
|
endpoint at <Mono>/mcp</Mono>, optionally negotiating a long-lived stream via
|
|
<Mono>text/event-stream</Mono> when the server wants to push updates.
|
|
</DocsP>
|
|
<DocsCode
|
|
label="single request"
|
|
code={`POST /mcp HTTP/1.1
|
|
Authorization: Bearer <jwt>
|
|
Content-Type: application/json
|
|
Accept: application/json, text/event-stream
|
|
|
|
{
|
|
"jsonrpc": "2.0",
|
|
"id": 1,
|
|
"method": "tools/list"
|
|
}`}
|
|
/>
|
|
|
|
<DocsH2 id="session">Session lifecycle</DocsH2>
|
|
<DocsList>
|
|
<DocsLi>
|
|
<Mono>initialize</Mono> — client sends protocol version + capabilities, server returns
|
|
its info and assigns a session id via the <Mono>mcp-session-id</Mono> header.
|
|
</DocsLi>
|
|
<DocsLi>
|
|
<Mono>notifications/initialized</Mono> — client confirms readiness. Server is now free
|
|
to push notifications.
|
|
</DocsLi>
|
|
<DocsLi>
|
|
<Mono>tools/list</Mono>, <Mono>tools/call</Mono>, <Mono>resources/list</Mono>,
|
|
<Mono>prompts/list</Mono> — the work.
|
|
</DocsLi>
|
|
</DocsList>
|
|
|
|
<DocsH2 id="why-mcp">Why MCP and not just REST</DocsH2>
|
|
<DocsP>
|
|
REST APIs need bespoke OpenAPI integration per client. MCP standardizes the discovery,
|
|
invocation, auth and streaming so any spec-compliant client picks up any spec-compliant
|
|
server with zero glue code. That's the entire point.
|
|
</DocsP>
|
|
</>
|
|
);
|
|
}
|