Skip to content

ACP: accept client-provided streaming-HTTP MCP servers #7

Description

@JAORMX

What's missing

The ACP adapter hard-rejects all client-provided MCP servers in session/new — including streaming-HTTP ones that mecatl is fully capable of consuming. mcpCapabilities is advertised {http:false, sse:false}.

Validated (independent cross-check, flagged by both reviewers):

  • rejectClientMCP rejects every client mcpServers entry; stdio is hard-rejected (correct — "no stdio MCP, ever"), but URL/streaming-HTTP servers are also rejected as deferred (internal/adapter/acp/agent.go).
  • mcpCapabilities{HTTP:false, SSE:false} advertised at initialize (agent.go).

Proposed approach

Accept client-provided streaming-HTTP MCP servers from session/new (mount them onto the session's MCP manager) and advertise mcpCapabilities.http: true. Continue to hard-reject stdio/command MCP servers (per the project invariant). Medium.

Part of ACP Phase 3 long-tail (docs/adr/0001-acp-adapter.md).

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions