Skip to content

Add Unstructured Transform MCP integration#540

Open
dizon-u10d wants to merge 1 commit into
deepset-ai:mainfrom
dizon-u10d:add-transform-mcp-integration
Open

Add Unstructured Transform MCP integration#540
dizon-u10d wants to merge 1 commit into
deepset-ai:mainfrom
dizon-u10d:add-transform-mcp-integration

Conversation

@dizon-u10d

@dizon-u10d dizon-u10d commented Jul 10, 2026

Copy link
Copy Markdown

Adds an integration catalog page for Unstructured Transform MCP, a hosted MCP server exposing Unstructured's document-processing pipeline (partition, enrich, chunk, embed) as MCP tools.

  • New: integrations/transform-mcp.md (type: Tool Integration)
  • Connects via the existing mcp-haystack MCPToolset over Streamable HTTP using StreamableHttpServerInfo's native token parameter; documents the mcp-remote OAuth fallback.
  • Reuses the existing /logos/unstructured.svg asset.

Docs: https://docs.unstructured.io/transform/overview · Get started: https://transform.unstructured.io/get-started

Companion cookbook PR: deepset-ai/haystack-cookbook#300

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 10, 2026

Copy link
Copy Markdown

@dizon-u10d is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

@dizon-u10d

Copy link
Copy Markdown
Author

Hi @kacperlukawski, following up on this listing for Unstructured Transform MCP (uses the existing mcp-haystack integration, same as integrations/mcp.md).

Verified against the live server: StreamableHttpServerInfo/MCPToolset correctly reaches https://mcp.transform.unstructured.io, and the server returns a clean 401 invalid_token with a spec-compliant OAuth-discovery challenge. One thing worth flagging: with eager_connect=True, an invalid/expired key doesn't surface that 401 right away, it hangs for mcp-haystack's ~30s connection timeout and then raises a generic MCPConnectionError, since the underlying mcp 1.28.1 SDK's streamable-http transport doesn't propagate the HTTP error out of its TaskGroup until the timeout fires. Not a defect in this doc, just something a user hitting a bad key would notice.

The only failing check here is the Vercel preview needing fork authorization. Happy to make any changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant