Skip to content

Split Altinity Cloud MCP gateway from local altinity-mcp  #133

Description

@BorisTyshkevich

The existing altinity-mcp binary serves local/single-cluster use cases: stdio, single ClickHouse target, and legacy HTTP/JWE/OpenAPI behavior.

Altinity Cloud needs a narrower gateway binary:

  • HTTP streamable transport only
  • OAuth required
  • no stdio/SSE
  • no JWE token routing
  • no OpenAPI
  • multicluster routing via /mcp/{cluster}
  • per-token/per-cluster dynamic tool catalog cache

This avoids adding many mutually exclusive runtime modes to the current binary and keeps local usage stable.
Possibly, we need to strip the OAuth functionality from "non-cloud" binary, too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions