docs: state that adopting service discoverability opts an app in to ICP MCP - #372
Merged
Merged
Conversation
…CP MCP The protocol's whole purpose is that an agent handed only an app's URL can work the rest out unattended, so publishing the manifest is the moment an app becomes usable by agents that read it. Say so on the page, above the fold, rather than leaving it implicit: adopting the protocol means the app agrees to be discovered by ICP MCP under its terms of service. Placed as a caution aside right after the intro, before the layer breakdown, so it is read before any of the instructions it qualifies.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds an early opt-in notice for apps adopting service discoverability.
Changes:
- Adds an ICP MCP discovery and terms-of-service caution.
Verified
- Reviewed placement, wording, and surrounding protocol scope.
- Live brand rules were unavailable; checked against loaded guidance.
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The notice said "implementing this service discoverability protocol", but the page goes on to say each of the five layers is independently adoptable. A reader could not tell whether exposing only a getApiDoc method or a derivation origin also opts their app in. Name the act: publishing the Layer 1 manifest at /.well-known/ic-architecture. That is also what ICP MCP actually keys on, so the page and the connector now agree.
aterga
commented
Aug 28, 2026
aterga
commented
Aug 28, 2026
sea-snake
approved these changes
Aug 28, 2026
Per review. Two changes to the same notice: The page description now says what the exposed data means, not only what it is: exposing it indicates the app's operations are intended to be used through ICP MCP, under its terms of service and privacy policy. The caution aside gains the privacy policy alongside the terms, and follows the review's phrasing (accept the terms, comply with the privacy policy). The description's links are plain prose rather than markdown. Starlight puts this field only into <meta name="description"> and <meta property="og:description">, which cannot render markdown, so link syntax there would show as literal brackets in search results and link previews. All three links are clickable in the aside, which is the part a reader actually sees.
…ntro Two review points. The description is now exactly the reviewer's edited suggestion: the short one-liner, without the consent sentence. My previous commit had folded that sentence in, from the earlier version of the suggestion, before it was edited. The consent statement stays where it renders and where a reader sees it, in the caution aside. The intro no longer speaks of an abstract "AI agent" but of an agent working through ICP MCP, which is what the page is actually about. The remaining plain "agent" mentions further down read naturally once the opening establishes which agent is meant, so they are left alone rather than rewritten wholesale.
aterga
marked this pull request as ready for review
August 28, 2026 14:27
marc0olo
approved these changes
Aug 28, 2026
Draft
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a visible disclaimer to
docs/guides/frontends/service-discoverability.mdstating that adopting the protocol opts an app in to being discovered by ICP MCP, under its terms of service and privacy policy.The protocol's whole purpose is that an agent handed only an app's URL can work the rest out unattended, so publishing the manifest is the moment the app becomes usable by agents that read it. The page did not say so. It does now, above the fold, before any of the instructions it qualifies.
Wording:
Two smaller changes came out of review: the page
descriptionnow names ICP MCP, and the opening line speaks of "an agent working through ICP MCP" rather than an abstract AI agent.Structural decisions
## The five layers, so it is read before the instructions it qualifies rather than being buried under them.:::caution(used 11 times elsewhere indocs/) rather than:::note, since the point was that it be clearly visible, and it carries an agreement rather than an aside.getApiDocor anii-derivation-originalso opts an app in. It does not, and naming the manifest makes the page agree with what the connector actually keys on (dfinity/imcp2#166 gates writes on exactly that document).description: Starlight puts that field only into the page'sdescriptionandog:descriptionmeta tags, which cannot render markdown, so links there would show as literal brackets in search results and link previews. The statement lives in the aside, where it renders and where a reader sees it.internetcomputer.org/icp-mcp/, verified live (HTTP 200; the pages render "ICP MCP Terms of Service" and "ICP MCP Privacy Policy").Verified
npm run buildpasses on every commit; the page renders the aside asstarlight-aside--cautionwith all links intact, confirmed on the deployed preview.dfx, no banned vocabulary (checked againsticp-brand-voice).agent-signalingblockquote and llms.txt footer, injected into every page by theagent-docsintegration; out of scope here.package-lock.json, touched bynpm installduring setup, is deliberately not included.Note for reviewers
@sea-snake approved at
b7e5e2b. Two further commits landed after that, both addressing review comments on this PR (d9fe5df,389828e), so the approving commit is no longer the head and the approval may need refreshing.