Skip to content

Say what the hosted MCP tools cost and where the plan boundary is - #17

Closed
chrisjleal wants to merge 1 commit into
mainfrom
fix/mcp-tool-costs
Closed

chrisjleal wants to merge 1 commit into
mainfrom
fix/mcp-tool-costs

Conversation

@chrisjleal

Copy link
Copy Markdown
Contributor

Search and page reads record 1 credit, a connected-app action records 2, a call relayed through a saved MCP server records 1, and a call on your own provider key records nothing. Saving a remote MCP server and running its tools are on Pro; listing, using and removing a saved server stay on every plan.

The research tools are a fallback for a client that has none, and the page says so.

Search and page reads record 1 credit, a connected-app action records 2, a call
relayed through a saved MCP server records 1, and a call on your own provider key
records nothing. Saving a remote MCP server and running its tools are on Pro;
listing, using and removing a saved server stay on every plan, and every other
tool runs on credits on every plan. The research tools are a fallback for a client
with none, and the page says so, because preferring the client's own search and
fetch is what keeps the bill honest.
@chrisjleal

Copy link
Copy Markdown
Contributor Author

Superseded by the boundary change: the per-call table here priced tools that no longer exist on the hosted MCP surface, and the plan boundary it documented is gone. The same pages are corrected in the new PR.

@chrisjleal chrisjleal closed this Oct 25, 2026
@chrisjleal
chrisjleal deleted the fix/mcp-tool-costs branch October 25, 2026 04:32
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