Why
hookdeck gateway mcp refuses to start against a non-Gateway project, but places no guard on switching to one mid-session.
hookdeck_projects use <outpost-project-id> succeeds. Every Gateway tool afterwards then 404s, while the server sits there apparently healthy. Nothing tells the agent what it did, and the session is left pointing at a project it cannot serve.
This is the same failure shape v2.5.0 spent nine fixes eliminating: the CLI silently doing something other than what was asked, with the first symptom being missing data rather than an error.
Current behaviour
|
Startup |
projects use mid-session |
gateway mcp |
rejects non-Gateway (there is a test for this) |
no guard — any project id is accepted |
outpost mcp |
rejects non-Outpost |
Outpost projects only |
The Outpost server sets a project-type filter; the Gateway server sets none.
What to do
Scope each product's MCP server to its own project type — list and switch. A server that can only serve one product should not list, or move to, projects it cannot serve.
Concretely, for gateway mcp:
The mechanism already exists in the shared MCP package (ProjectFilter); Gateway just does not set it.
Considered and rejected
Listing every project with its type and refusing only on use. It gives more visibility, but shows projects the server can never act on, and makes the useful case (one product, several projects) noisier for no benefit. Filtering is the clearer contract.
Why
hookdeck gateway mcprefuses to start against a non-Gateway project, but places no guard on switching to one mid-session.hookdeck_projects use <outpost-project-id>succeeds. Every Gateway tool afterwards then 404s, while the server sits there apparently healthy. Nothing tells the agent what it did, and the session is left pointing at a project it cannot serve.This is the same failure shape v2.5.0 spent nine fixes eliminating: the CLI silently doing something other than what was asked, with the first symptom being missing data rather than an error.
Current behaviour
projects usemid-sessiongateway mcpoutpost mcpThe Outpost server sets a project-type filter; the Gateway server sets none.
What to do
Scope each product's MCP server to its own project type — list and switch. A server that can only serve one product should not list, or move to, projects it cannot serve.
Concretely, for
gateway mcp:hookdeck_projects listreturns Gateway projects onlyhookdeck_projects userefuses a non-Gateway project, with a message naming the type and pointing at the other serverThe mechanism already exists in the shared MCP package (
ProjectFilter); Gateway just does not set it.Considered and rejected
Listing every project with its
typeand refusing only onuse. It gives more visibility, but shows projects the server can never act on, and makes the useful case (one product, several projects) noisier for no benefit. Filtering is the clearer contract.