Add Unstructured Transform MCP starter template

[SudSampath]

What changed

• Added a reusable MCP server template list to the Add MCP Server modal.
• Added Unstructured Transform as a starter template with the streamable HTTP endpoint and Authorization header placeholder.
• Clarified what Unstructured Transform does: converts PDFs, DOCX, PPTX, HTML, and images, including scanned/image-only pages via OCR, into clean markdown, JSON, HTML, or text, with RAG preprocessing for chunking, enrichment, and embedding.
• Documented the Unstructured setup flow in the MCP tools docs, including the required UNSTRUCTURED_API_KEY environment variable and allowlist domain.

Why

Unstructured Transform is exposed as an MCP server, so discoverability fits best as a first-class MCP starter configuration instead of a guessed native REST connector. Selecting the template fills the server name, URL, transport, timeout, and header values while still using Sim's existing connection test and MCP execution flow.

Validation

• pnpm dlx @biomejs/biome@2.0.0-beta.5 check --no-errors-on-unmatched --files-ignore-unknown=true ...
• git diff --check

Full workspace checks were not run in this fresh clone because Bun is not installed in the local shell and dependencies are not installed.

[vercel]

Someone is attempting to deploy a commit to the Sim Team on Vercel.

A member of the Team first needs to authorize it.

[SudSampath]

Quick follow-up / product context:

This PR is meant to be the small MCP-first step: it gets Unstructured Transform into the MCP add flow so a Sim user can pick it, add their UNSTRUCTURED_API_KEY, and use the hosted Transform MCP server in agents/workflows.

For folks less familiar with it: Transform converts documents like PDFs, DOCX, PPTX, HTML, and images, including scanned/image-only pages via OCR, into clean markdown, JSON, HTML, or text. It also supports the RAG prep work around that: chunking, enrichment, and embedding.

If we want Transform to show up in the main Integrations catalog too, I think there are two possible follow-ups:

• MCP-backed integration card — my preferred path if it fits Sim's product model. Keep execution backed by the hosted MCP server, add a normal catalog card/page with icon/category/tags/docs, and have Add to Sim open or prefill this MCP template.
• Native Sim block/tool — definitely possible, but heavier. We'd need REST/OpenAPI docs, auth details, file upload/reference behavior, exact request/response schemas, sample successful responses, supported operation choices, and Unstructured brand assets. I avoided that here because the public quickstart is MCP-first, and I didn't want to guess a Sim-native schema.

Happy to adapt this to whatever pattern the Sim team prefers. If MCP-backed catalog cards are acceptable, I can follow up with that PR.