AgentDrive's MCP endpoint (https://drive.mcp.tokencanopy.com/mcp) currently authenticates OAuth 2.1 PKCE only. From agentdrive-sdk/docs/auth.md:
"Authentication uses OAuth 2.1 with PKCE (Proof Key for Code Exchange). No API key to paste: the MCP client handles the flow automatically on first tool use."
That works for interactive MCP hosts (Claude Code, Cursor) but not for server-side agents that run headless and need a static credential. e2a's MCP already supports the dual model - from tokencanopy/e2a README (## MCP server):
"Authenticate either with OAuth 2.1 (add e2a as a connector and authorize in the browser) or a Bearer API key (Authorization: Bearer <e2a API key>). An agent-scoped credential resolves its agent server-side; account-scoped callers pass the agent email per tool call."
Request: add a Bearer API-key auth path to the AgentDrive MCP authorization server, matching e2a's behavior - an agent-scoped key resolves the caller's drive/agent server-side so headless agents can connect with a static key minted in the console (app.tokencanopy.com), no browser flow required.
Concrete consumer: Instinct (our own agent) calls e2a's REST API with a vaulted agent-scoped key today but cannot use AgentDrive's MCP endpoint at all without an interactive OAuth flow.
AgentDrive's MCP endpoint (https://drive.mcp.tokencanopy.com/mcp) currently authenticates OAuth 2.1 PKCE only. From
agentdrive-sdk/docs/auth.md:That works for interactive MCP hosts (Claude Code, Cursor) but not for server-side agents that run headless and need a static credential. e2a's MCP already supports the dual model - from
tokencanopy/e2aREADME (## MCP server):Request: add a Bearer API-key auth path to the AgentDrive MCP authorization server, matching e2a's behavior - an agent-scoped key resolves the caller's drive/agent server-side so headless agents can connect with a static key minted in the console (app.tokencanopy.com), no browser flow required.
Concrete consumer: Instinct (our own agent) calls e2a's REST API with a vaulted agent-scoped key today but cannot use AgentDrive's MCP endpoint at all without an interactive OAuth flow.