Currently, the oci-cloud-mcp-server appears to require a specific OCI profile to be preloaded or defined at startup (e.g., via environment variables or a static config). This limits the ability to interact with multiple OCI tenancies or regions without restarting the server.
I would like to propose adding support for "on-the-fly" profile selection. This would allow the MCP to utilize different profiles defined in the ~/.oci/config file dynamically based on the request context.
Reasoning
Flexibility: Users often manage multiple environments (Dev, Test, Prod) across different tenancies.
Efficiency: Eliminates the need to run multiple instances of the MCP server on different ports just to access different profiles.
Currently, the oci-cloud-mcp-server appears to require a specific OCI profile to be preloaded or defined at startup (e.g., via environment variables or a static config). This limits the ability to interact with multiple OCI tenancies or regions without restarting the server.
I would like to propose adding support for "on-the-fly" profile selection. This would allow the MCP to utilize different profiles defined in the ~/.oci/config file dynamically based on the request context.
Reasoning
Flexibility: Users often manage multiple environments (Dev, Test, Prod) across different tenancies.
Efficiency: Eliminates the need to run multiple instances of the MCP server on different ports just to access different profiles.