# Skill: Advertise Machine Surfaces via RFC 8288 Link Headers

> **Standard:** RFC 8288
> **Category:** DISCOVERABILITY
> **Classification:** SPECIFICATION_AND_GUIDE
> **Author:** TinyCTO Architecture Guild (https://tinycto.tv)

## Overview
Implement RFC 8288 HTTP Link response headers to advertise machine-readable endpoints (MCP server cards, API catalogs, llms.txt) on every HTML response.

## Learning Objectives
1. Include rel='mcp-server-card' linking to /.well-known/mcp/server-card.json.
2. Include rel='service-doc' and rel='api-catalog' linking to discovery manifests.
3. Prevent header bloat while providing instant discovery on HEAD/GET requests.

## Prerequisites
- Next.js next.config.ts or reverse proxy header manipulation

## Implementation & Execution Guide

### Step 1: Configure Link Headers in Next.js
Add discovery links to the global headers pipeline.

```http
Link: </.well-known/mcp/server-card.json>; rel="mcp-server-card", </.well-known/api-catalog>; rel="api-catalog", </llms.txt>; rel="service-doc"
```

## Architectural Takeaway
RFC 8288 Link headers allow AI agents to discover machine interfaces without parsing the DOM tree.