Remote MCP servers configured with type: remote in altimate-code.json cannot use dynamic authentication. APIs like Microsoft Fabric require bearer tokens that expire (~1hr), but the config only supports static header values. There's no way to use shell command interpolation (e.g. $(az account get-access-token ...)) or a token-refresh mechanism, making remote MCP servers unusable for auth-protected endpoints without manual token rotation.
Metadata
| Field | Value |
|---|
| CLI Version | 0.7.0 |
| Platform | darwin |
| Architecture | arm64 |
| OS Release | 24.3.0 |
| Category | bug |
| Working Directory | microsoft-fabric |
| Session ID | ses_208c8b2b3ffeDa9djtWwkgdFGN |
Remote MCP servers configured with
type: remotein altimate-code.json cannot use dynamic authentication. APIs like Microsoft Fabric require bearer tokens that expire (~1hr), but the config only supports static header values. There's no way to use shell command interpolation (e.g.$(az account get-access-token ...)) or a token-refresh mechanism, making remote MCP servers unusable for auth-protected endpoints without manual token rotation.Metadata