Create a general API MCP server for OCI APIs

[gebhardtr]

Moved from: https://github.com/shrug-labs/oci-mcp/issues/9

Generally, tools that map 1:1 to API endpoints tend to be too granular and confuse models but they are a good
starting point/fallback in the case that the curated servers don't work as desired:

Approaches:

• automatically generate the MCP servers offline and upload the servers without exposing the specs
• create an "SDK tool" instead of an API tool that converts the SDK packages into tools
• drive the OCI CLI instead of the APIs directly (which seems to be the best approach so far based on the fact that the external API definitions are EoLd) (this is our planned approach unless the others pan out); alternatives/notes:
  • Convert CLI commands into SDK calls
  • Drive the CLI in a container/sandbox
• (details below) process the OpenAPI specs for all OCI APIs; this would be ideal -- the external API definitions would be significantly complemented by docs and other examples that the available models have been tuned on and would allow us to reduce the size of the context. Unfortunately, external API definitions are EoLd and happen to be a side-effect of the docs publishing process and can't be relied on.

Notes:

• OCI API pecs: https://docs.oracle.com/en-us/iaas/api/specs/index.json
• FastMCP integration: https://gofastmcp.com/integrations/openapi
• Authentication:
  • https://gofastmcp.com/integrations/openapi#authentication
  • https://docs.oracle.com/en-us/iaas/Content/API/Concepts/signingrequests.htm#five
• invoking command line utilities from programs can be perilous; we'll need guardrails, validation and sanitization.