Link Header Support

You advertise API endpoints via HTTP Link headers by emitting RFC 8288 Link relations such as api-catalog, service-desc, service-doc, and describedby with their target URLs. This allows clients to automatically locate API descriptors and MCP server metadata.

RFC 8288 Link header service discovery is a mechanism that provides machine-readable pointers to API catalogs, OpenAPI specs, and documentation. It allows automated integrations and agent tooling to self-configure by fetching Link headers instead of using hardcoded URLs.

Yes, MCP tooling can automatically locate server metadata by fetching Link headers. The headers publish describedby relations that point to MCP server-card metadata, enabling agents to bootstrap and find endpoints without manual configuration.

You set up automated API discovery by emitting a service-desc Link relation in your HTTP responses that points to your OpenAPI specification. Clients and crawlers can then read this header to reliably locate the correct API descriptors for your environment.

Yes, Link header support works for client bootstrapping without hardcoded URLs. By publishing relations for api-catalog, service-doc, and service-desc, clients can dynamically fetch target URLs to locate endpoints and metadata required for integration setup.