Documentation
MatteUse Matte from your agent
Updated
Matte includes a small MCP server for inspecting background-removal jobs. It is read-only and metadata-only: an agent can see whether jobs are queued, processing, done or failed, but it never receives image data or storage paths, and it cannot submit, change or delete anything.
Reaching it
The MCP server is mounted at /mcp on your Matte environment and is set up for delegated access, so you reach it through Scalpels rather than by connecting to it directly. Install the Scalpels MCP server in your agent with a token that has the Call installed apps ability, and your agent can list the MCP-enabled products your team runs, see Matte's tools, and call them on a specific deployment. Scalpels relays each call with your identity and your role on the team. See Use Scalpels from your agent for setup and Console for how delegated access works.
Tools
job_status
Returns the status of one job.
| Argument | Required | Meaning |
|---|---|---|
job_id |
Yes | The job's UUID, as returned by POST /v1/remove. |
The answer carries the job's id, status, created_at and updated_at, and an error field. For a failed job, error is the fixed value job_failed, not the underlying error message; the message is available only from the API's status route. An unknown id returns job_not_found.
recent_jobs
Lists jobs newest first, with the same fields as job_status.
| Argument | Required | Meaning |
|---|---|---|
status |
No | Only jobs with this status: queued, processing, done or failed. |
created_from |
No | Only jobs created at or after this ISO-8601 timestamp. |
created_to |
No | Only jobs created at or before this ISO-8601 timestamp. |
limit |
No | How many jobs to return, from 1 to 100. Defaults to 25. |
cursor |
No | The next_cursor from a previous call, to fetch the next page. |
Each page returns jobs and a next_cursor, which is null on the last page. A cursor only works with the same filters it was issued for. created_from must not be later than created_to.
What to ask
Are any Matte jobs stuck in processing?
How many background removals failed today?
Check on Matte job 01a0cb3d-484f-7194-82ce-f310e5938786.
For a failed or stuck job, the agent can tell you which jobs are affected and when they started; to see why, check the error from the API's status route and the queue's failed jobs, as described in Troubleshooting.