MCP servers configured in .altimate-code/altimate-code.json (both "type": "remote" and "type": "local") are not automatically activated as callable tools at session start. The expectation is that these MCP servers should be auto-activated during session initialization so their tools are immediately available to the agent. Instead, the servers appear in list-config but their tools are not available to the agent during the session. The token was verified as valid (not expired), so authentication is not the issue. Workaround: using curl/bash to call the APIs directly.
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_208b53b2afferGYrXIa1PH9rvA |
MCP servers configured in
.altimate-code/altimate-code.json(both"type": "remote"and"type": "local") are not automatically activated as callable tools at session start. The expectation is that these MCP servers should be auto-activated during session initialization so their tools are immediately available to the agent. Instead, the servers appear inlist-configbut their tools are not available to the agent during the session. The token was verified as valid (not expired), so authentication is not the issue. Workaround: using curl/bash to call the APIs directly.Metadata