Compoid MCP

Required:
    file_upload: the file to attach. Accepted: (1) a data URI
        'data:<mime>;base64,<b64>' (base64-encode client-side files), or (2) a
        path on the MCP server host such as '/projects/...' (e.g. the path
        returned by Compoid_upload_file). Plain client-local paths are NOT
        accessible to the server.
    creators: non-empty list of author / AI-model names (e.g.
        ['John Doe']); for AI-generated content include the model name
        as a co-creator (e.g. ['Qwen']).
    keywords: non-empty list of tags (e.g. ['Compoid', 'MCP']) - records
        without keywords are hard to discover.

Recommended (thin records are hard to discover and may be rejected):
    title, description: a clear title and abstract.
    resource_type: one of analysis, image, video, audio, publication, document,
        software, project, dataset, presentation, workflow, tutorial, event, crypto, forex, indices,
        equities, physicalobject, model, other -
        any other value is rejected with 400 'Not a valid value.' (when omitted
        it is inferred from the file MIME type).
    subjects: up to 5 subject display names from the Compoid subject vocabulary
        (https://www.compoid.com/subjects); invalid names cause a 400.
        "Artificial Intelligence" is always appended as a default subject.

Optional:
    community_id: community slug (e.g. 'physics' - browse
        https://www.compoid.com/communities or use Compoid_search_communities),
        a community UUID, or a home-community slug 'user-<id>'. When omitted,
        the record is submitted to the API token's own home community
        (resolved via Compoid_whoami).

The record is tombstoned and drops out of all search results. Use it to
clean up test records. Only PUBLISHED records can be deleted - drafts have
no PID until they are published, so a draft must be published first (or
cancelled via the review flow) before it can be addressed this way.

The API token's user must be the record's creator or an owner of the record's
community; otherwise the API returns 403.

Required:
    work_id: the record to delete - a published record PID (e.g.
        '4171t-rc787'), a full record URL
        (https://www.compoid.com/records/<pid>), or its OAI.

On success returns a confirmation (HTTP 204). On failure the error includes
an actionable hint (403 = wrong user/permissions, 404 = not found or draft).

Only pass the fields you want to change; unprovided fields keep their current
values. An update with no changed fields is rejected as a no-op.

Required:
    work_id: the record to update - a published record PID (e.g.
        '4171t-rc787'), a full record URL, or its OAI. Drafts have no PID until
        published, so only published records can be updated.

Optional (any subset):
    file_upload: replacement file (data URI or MCP-server-host path) - only when
        replacing the file.
    title, description, creators, keywords, references: metadata to change.
    resource_type: must be one of analysis, image, video, audio, publication,
        document, software, project, dataset, presentation, workflow, tutorial, event,
        crypto, forex, indices, equities, physicalobject, model, other - any other value is rejected with 400 'Not a valid value.'
    subjects: up to 5 subject display names
        (https://www.compoid.com/subjects). Omit to keep the record's existing
        subjects; "Artificial Intelligence" is always appended as a default.