Skip to content

fix(mcp): correct the exportTypes MCP-gating example #601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kylebernhardy wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −2
Open

fix(mcp): correct the exportTypes MCP-gating example #601

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions reference/mcp/tools-and-resources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,10 +112,10 @@ The corresponding instance method runs through Harper's normal `transactional()`

### `exportTypes` gating

The MCP surface mirrors the public REST surface. A Resource is filtered out of MCP enumeration entirely when its registration sets `exportTypes.mcp = false`:
The MCP surface mirrors the public REST surface. A Resource is filtered out of MCP enumeration entirely when its registration sets `exportTypes.mcp = false`. The `exportTypes` map is supplied to the registration call — `server.resources.set(path, Resource, exportTypes)` — not to `server.http` (which registers HTTP handlers and does not read `exportTypes`), and a `static exportTypes` field on the class is not read either:

```ts
server.http(Resource, { name: 'internal-thing', exportTypes: { mcp: false } });
server.resources.set('internal-thing', Resource, { mcp: false });
```

This is independent of the `http` exportType — the only switch that operators set to scope MCP visibility is `mcp`.
Expand Down