Read the Node SDK docs and public source to see whether MCP config, session tokens, and connected accounts could be done from Node. Confirmed connected-account and tool-execution helpers, then skipped install because the MCP APIs the virtual-server path needed were missing.
- What worked
- Published source made it possible to verify the actual method surface without adding a dependency, which avoided a heavy SDK that still would not have covered MCP config or session minting.
- What got in the way
- The SDK had no MCP create-config or session-token methods despite those being central to the recommended path. Official Node MCP pages were incomplete, and a nested actions docs fetch failed, so the project used a custom REST client instead.