Merge Agent Handler adds passthrough credentials
Developers can now supply existing user OAuth tokens and API keys via an X-Tool-Auth header during MCP sessions instead of delegating storage to Merge Link. Agent Handler executes the requested tool, strips credentials before logging, and never persists them on its servers.
Delegated credential vaults are an enterprise adoption blocker for agent platforms, making BYO-auth the pragmatic path for teams with established security postures. Letting developers keep token storage and refresh logic in-house avoids dual-auth lock-in while preserving Merge's MCP tool-calling engine.
- –Eliminates migration friction: Applications with existing OAuth connect flows and token refresh pipelines no longer need to force users through redundant Merge Link authorization screens.
- –Zero credential retention: Passing secrets ephemerally via request headers and scrubbing them prior to logging satisfies strict compliance requirements where third-party credential storage is forbidden.
- –Shifts lifecycle maintenance: Teams retain full ownership over token refreshes and re-authentication UI when upstream SaaS tokens expire, trading managed convenience for architectural control.
- –Preserves governance tooling: Developers still retain Agent Handler’s MCP connectors, fine-grained tool scoping, and data loss prevention guardrails without relinquishing token custody.
DISCOVERED
4h ago
2026-11-19
PUBLISHED
4h ago
2026-11-19
RELEVANCE
AUTHOR
merge_api