OAuth-first connection
Compatible clients discover authorization metadata, open Audream Web for consent, and receive a resource-bound token.
Audream remote MCP
Use OAuth authorization, resource-bound tokens, and separate read, write, process, and delete scopes instead of pasting an API key into an agent client.
WHAT THE PLATFORM COVERS
Compatible clients discover authorization metadata, open Audream Web for consent, and receive a resource-bound token.
Default authorization requests Note read and processing access; write and delete scopes are requested only when needed.
Each operation validates its required scope before reading, changing, processing, or deleting user content.
Delete tools require a confirmation value that exactly matches the target Note ID.
START WITH A REAL WORKFLOW
Follow the published authentication boundary for this interface. Keep credentials out of browsers, mobile apps, firmware, logs, and source control.
Remote MCP URL
https://audream-api.tulingbc.com/mcp
Default scopes
notes:read notes:processIMPLEMENTATION BOUNDARIES
The client discovers OAuth metadata, opens Audream Web for consent, and receives a resource-bound access token. Default authorization requests read and processing access.
Tool errors preserve authentication, scope, processing, and target-not-found distinctions. Clients must not convert an incomplete operation into success.
Delete tools require notes:delete and a confirm_note_id value that exactly matches the target Note ID.
The detailed contract, current installation steps, scopes, and operation schemas remain in the versioned Audream documentation.
Open the complete documentation ↗DELIVERY
KEEP EXPLORING
A PRODUCT, NOT A PILE OF PARTS