Skip to content

MCP tools by plan, saved keys and remote servers on every plan - #20

Merged
chrisjleal merged 3 commits into
mainfrom
release/launch-boundary-and-security
Oct 25, 2026
Merged

chrisjleal merged 3 commits into
mainfrom
release/launch-boundary-and-security

Conversation

@chrisjleal

@chrisjleal chrisjleal commented Oct 25, 2026 •

Copy link
Copy Markdown
Contributor

The MCP tool reference states what a signed-in connection gets on every plan: the proof and permission tools, jobs, the hosted browser, connected apps, remote MCP servers, session notes, saved tools, web search, page fetch, and saved keys (list, remove, or call a provider with one). Saving a key happens on the profile, never through a tool. Pricing lists the per-call rates; the privacy table, OAuth scope table, secrets page, jobs page, overview and changelog say the same.

Docs validation and route checks pass.

chrisjleal and others added 3 commits October 25, 2026 12:00
Jobs, the hosted browser, connected apps, session notes, saved tools, web search and page
fetch are on every signed-in connection, on credits. The tools, jobs, pricing, overview
and privacy pages said a connection refused them. They now list them with the per-call
rates, and name the three things that stay off a connection: saving a key, spending a
saved key, and relaying to a remote MCP server.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A call to a vault or relay tool on a connection is rejected as an unknown tool, because
the connection is never offered it. The copy said it answered platform_only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Listing or removing a saved key, calling a provider with one, and running a saved remote MCP
server are on every signed-in connection, metered like the other calls. Only saving a key
stays off a connection; it happens on the profile.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chrisjleal
chrisjleal merged commit d619293 into main Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant