Skip to content

document-loader: Documentation implies HTTP transfer support #2443

@danielmarquard

Description

@danielmarquard

Describe the issue

The documentation for the document loader MCP implies that HTTP transport is supported when running with Docker, but the Dockerfile exposes no ports and the container confirms stdio transport at launch. I could really use these tools, but stdio won't cut it for running these tools at scale.

Edit: I modified the project to support streamable HTTP. Works great. But it'd be better if HTTP transport was officially supported.

Links

https://github.com/awslabs/mcp/blob/main/src/document-loader-mcp-server/README.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationneeds-triageThis needs to be handled, it is the first automatically assigned label to issues.

    Type

    No type

    Projects

    Status

    To triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions