Changelog and Migrations
Changes that affect authentication, discoverable tools, client setup, and automated workflows.
July 2026
Authentication-required brand MCP
- • All
/mcprequests now require OAuth or a Bearer API key. - • Unauthenticated requests return HTTP 401 and JSON-RPC
-32002. - • OAuth sessions can carry multiple authorized brands and per-brand permissions.
- • The base brand manifest is four tools; Partner Program adds audit, source, monitoring, whitespace, and publication tools.
- • Business Profile writes moved to Enterprise and require an exact approved action plus idempotency.
- • The public documentation now covers the hosted brand MCP only.
Migration checklist
- 1Add OAuth or an Authorization: Bearer osk_… header to every MCP request.
- 2Call tools/list after authentication instead of relying on a hardcoded tool count.
- 3For multi-brand OAuth users, list accessible brands and pass brand_id to brand-bound tools.
- 4Replace deprecated tool names with the current mappings below.
- 5Update Business Profile write workflows to create, approve, and idempotently execute the exact action.
- 6Treat the npm stdio adapter as a legacy interface rather than an equivalent hosted-MCP client.
Removed and renamed tools
| Older name | Current guidance |
|---|---|
| discovery_intent | Use the current core brand tools and agent prompts. |
| category_deep_dive | Removed from the hosted MCP manifest. |
| ai_readiness_check | Use brand_narrative_check and brand_action_plan. |
| find_brands_by_product | Removed from the hosted MCP manifest. |
| parent_company_map | Removed from the hosted brand MCP manifest. |
| archetype_examples | Removed from the hosted MCP manifest. |
| brand_vs_brand | Use brand_compare. |
| claim_pitch | Removed from the hosted MCP manifest. |
| directory_feedback | Removed from the hosted MCP manifest. |
| suggest_category | Removed from the hosted MCP manifest. |
Legacy npm adapter
The published stdio package is a separate three-tool adapter over the legacy invocation endpoint. It does not expose the current remote MCP's OAuth, Business Profile, audit, source, monitoring, approval, prompt, or resource capabilities. New integrations should connect directly to https://scout.optimly.ai/mcp.
Start with the current connection guide.
