MCP
What the connector can do
The connector can list and edit the plan, report tasks, link an issue, and publish a file. It does not decide reviews or change who is on the team.
The tools follow the same rules as the web app. A read-only connection does not offer the edit tools. A connection without publish does not offer uploads. Removing something archives it. Nothing here is thrown away.
The plan
Start with the project list. A token sees only its one project. From there the client can list animation sets, requirements and relationships, and read one requirement, including an archived one.
With write, it can create, update, archive and restore a requirement. Archiving a requirement also archives its parts and their relationships. Restoring the requirement brings them back. A relationship can be created, updated or archived. A single relationship has no restore. Create it again.
Tasks and issues
Tasks are derived from the work. The client can list yours, list a project's, and read one. It cannot create a task or mark one complete. The task leaves the list when the underlying record is done.
It can list linked issue trackers and the links on a requirement or an asset, add a link, refresh it, or archive it. The tracker itself stays read-only. Linking an issue does not change the issue in Jira, Linear or Cheats.
Files
Files belong to an asset version, not directly to a requirement. publish_asset_version publishes a file as a new version, creating the asset by name if needed, and can link it to the requirements it fulfils. A small file can be sent with the call. A larger one is uploaded first with the command from request_upload, then published by its hash. Publishing the same bytes again does not create a second copy.
The demo does not accept uploads. On Cloud the file goes to the organisation's own storage bucket, which Pro can connect.
Left to the app
Reviews and verdicts, members, tokens, billing, and creating a project are done in AnimSync, not through these tools. The client should send you there.