Aspect hosts a remote Model Context Protocol server, so AI tools you already use can browse, search, and organize your media library directly:
It is a Streamable HTTP MCP endpoint. Tools run through the same operation layer as the REST API and the in-app assistant, so behavior and permissions are identical everywhere.
Authentication
Two options:
- OAuth sign-in: clients that support MCP OAuth (Claude, ChatGPT, Cursor, and others) prompt you to sign in to your Aspect account when you add the server. This is the easiest path.
- API key: send an Aspect API key (
sk_...) as a Bearer token in the Authorization header. Use this for clients or scripts that can attach explicit headers. See the API overview for how to create a key.
Either way, every tool call is checked against your own workspace, project, directory, collection, and asset permissions - the MCP server can never do more than you can.
Connecting a client
Claude
ChatGPT
Cursor
Other clients
- In Claude Desktop or claude.ai, open Settings, then Connectors.
- Click Add custom connector.
- Paste the Aspect server URL:
https://api.aspect.inc/mcp
- Click Connect and sign in to Aspect when prompted.
- Open Settings and turn on Developer mode (Connectors).
- Add a new connector / MCP server.
- Paste the server URL:
https://api.aspect.inc/mcp
- Sign in to Aspect when prompted.
- Open Settings, then MCP, and add a new server (or edit
~/.cursor/mcp.json).
- Add the configuration below.
- Sign in to Aspect when prompted.
Add Aspect as a remote (Streamable HTTP) MCP server and authorize with your Aspect account when your client prompts you:If your client does not support OAuth sign-in, configure an Authorization: Bearer sk_... header with your API key instead:
The same setup instructions are available in the web app under Settings → Agent & MCP, with copyable snippets per client.
Workspaces
Projects
Directories
Assets
Search
Transcription
Collections
Share links
Other
What MCP does not expose
Some operations are deliberately unavailable through MCP:
- Uploads and downloads: no upload endpoints, download URLs, or storage tokens.
- High-impact deletions: workspace create/delete and project delete are not exposed. Asset and directory delete tools move items to the project trash rather than permanently deleting them, and there is no empty-trash or permanent-delete tool.
- Public share sessions: share password reveal and public share sessions are not available.
Use the REST API for these workflows.