| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Let's hold on merging until the AI Catalog PR lands |
Sorry, something went wrong.
|
@SamMorrowDrums it's landed so let's get this in |
Sorry, something went wrong.
Adapt the MCP Catalog Entry to AI Catalog PR #37 / ADR 0014, which renames the CatalogEntry `mediaType` member to `type` and reframes its description as an open-text type identifier rather than a strict IANA media type. Scoped to the field rename only. The value remains `application/mcp-server-card+json` (this repo's deliberate choice per issue ADR 0014's known-type `application/mcp-server+json`. The Server Card's own HTTP media type (Accept/Content-Type) is unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
What
Adapts the MCP Catalog Entry in docs/discovery.md to AI Catalog PR #37 / ADR 0014, which renames the CatalogEntry.mediaType member to type and reframes its description as an open-text type identifier rather than a strict IANA media type.
Changes (docs-only, docs/discovery.md):
Rebase / conflict resolution
This branch was rebased onto the current main to resolve a merge conflict in docs/discovery.md. The conflict came from changes that landed on main after this branch was cut:
The resolved diff is exactly the mediaType → type rename (table row, four examples, validation prose) applied on top of main — nothing from either side's intent was dropped.
Scope decision — value deliberately kept as application/mcp-server-card+json
This PR renames the field only. The value stays application/mcp-server-card+json and is not changed to ADR 0014's known-type application/mcp-server+json. Rationale:
Flag for maintainers: AI Catalog's ADR 0014 known-types list uses application/mcp-server+json for MCP. Whether this repo should also adopt that value (reversing issue #9 / PR #18 and re-introducing the server.json naming collision) is a separate, more consequential decision and is intentionally out of scope here. Happy to file a cross-repo issue if maintainers want to pursue it.
What is intentionally NOT changed
Verification
🤖 Generated with Claude Code