Skip to main content

​
The client cannot connect

Use https://api.aspect.inc/mcp and select Streamable HTTP. This is the media platform server. A documentation-search MCP offered by the docs site serves a different purpose. Refresh or restart the client connection after changing its configuration. For OAuth, complete the Aspect sign-in. For an API key, check that the client sends the key as a Bearer token without exposing it in a prompt or log.

​
Connected, but the project is missing

Ask for workspaces_list, then projects_list for the expected workspace. Check the signed-in account and its permissions. Knowing an asset ID does not grant access to it. When combining MCP with the CLI, also run aspect auth status --json. They authenticate separately and can be signed in as different accounts.

​
Search or transcripts return no content

Check the project ID and use assets_search_capabilities to discover valid search channels and filters. Verify that the source is uploaded and processed. Indexed captions, transcripts, or document text may not exist yet, and a selected time range or track can have no entries. Try a known filename or list the containing directory to distinguish missing access from a search query with no matches.

​
A copy or generation returned an ID, but no file is ready

A job or run ID records accepted background work. It is not a completion signal. Inspect the copy destination and expected files; use generations_run_get for a generation. Check for processing errors before starting dependent work. For local CLI work, aspect transfer status <id> --json reports detached transfers, while aspect pin list --json reports offline pins. These are different systems; a cloud copy job ID is not a CLI transfer ID.

​
The agent cannot copy proxies, mount files, or edit a timeline

The remote MCP copy tool does not currently expose the proxy-copy option. Use Aspect’s Copy videos as proxies action or the REST request in Agentic Video Editing. Mounts, local transfers, and pins use the CLI. Timeline edits use the editor’s own integration. Connecting Aspect MCP alone does not install an editor integration or make a local drive available to a cloud-only agent.

​
A tool is missing or rejects an argument

Refresh the connection and inspect the tools and input schemas your client actually exposes. Client prefixes can differ from the names in the tool reference. Use a returned resource ID, respect required fields, and remove arguments that are not in that tool’s schema. Batch operations where a list is supported. For large libraries, follow the tool’s pagination instead of increasing the request indefinitely.