Machine access

AI, API & OAuth

authenticated

MCP OAuth

Recommended for interactive AI clients.
PKCE
MCP resource
Loading…
Protected Resource Metadata
Loading…
Authorization Server Metadata
Loading…
?m access tokens?d refresh tokensno CIMDDCR off

Legacy API key

scripts / fallback

API keys remain supported for scripts and older clients. Interactive MCP clients should prefer OAuth.

Pre-register OAuth client

Useful when an MCP client does not publish a Client ID Metadata Document.

OAuth clients

0 active
ClientTypeScopesTokensLast used
No OAuth clients have connected yet.

Authorized clients

0 active grants
ClientUserScopesAuthorizedTokens
No clients have been authorized yet.

Browser Capture

write-only

Generate a key that can only send captures into Engram.

Scope
capture:write

Remote MCP

OAuth preferred
Endpoint
https://YOUR-HOST/mcp

Modern MCP clients can discover OAuth automatically from the protected resource metadata. Legacy Bearer API keys still work.

Legacy API credentials

0 active
NamePrefixScopesLast used