Archestra Community · Slack
MCP tools unavailable: could not connect to MCP Gateway . Agent is shared with the team, MCPs are shared with the team with added service accounts shared with this team. So the setup appears to be correct.Root cause: When your team token authenticates an A2A SendMessage call, a2a-manager.ts correctly identifies you as a team actor at auth time, but then discards that identity before execution, replacing it with a "system" sentinel string. Downstream, the MCP gateway token selector tries to find a token by checking "system"'s team memberships — which is always empty — so it can never recover your team's own token. It falls back to an org-wide token, which either doesn't exist or isn't authorized for your agent's MCPs, and that failure surfaces as "could not connect to MCP Gateway."
This same bug pattern was already fixed elsewhere in the codebase, just never ported over to this path: launch-spec.ts's resolveGatewayToken() branches on actor.kind explicitly — for a "team" actor it calls TeamTokenModel.findTeamToken(teamId) directly, looking the token up by team ID with no userId/membership indirection at all. The plain SendMessage path in a2a-manager.ts has no equivalent branch — it always resolves tokens through a userId, so once a team actor is collapsed to "system" there's no way back to its own token.platform-v1.4.0-rc.27), I am attaching a patch here. Please let me know how would you like to proceed with this:Read-only live mirror of the Archestra Slack
Join us on Slack