Docs/BYOLLM
Bring your own LLM
OpenSuiteMCP does not run a shared model account. You attach providers in settings, pick one per chat, and tokens bill to that key or endpoint.
Named cloud providers
Google, Anthropic, and OpenAI are always in the list. Save extra named copies (up to 10 providers total) when a team has more than one key. Each chat picks a provider and a Speed or Reasoning model from that provider’s live catalog.
Custom HTTPS endpoint
Add an OpenAI-compatible base URL you operate — LiteLLM, vLLM, a corporate proxy, and similar. The app lists models from that URL and sends chat + tool context there. HTTPS is the default; HTTP is allowed only for localhost or a literal IP.
This is your LLM path. It is not an air-gapped NetSuite stack: MCP tool calls still go to Oracle’s AI Connector for the account you connect.
Keys at rest
Provider API keys (and NetSuite OAuth tokens) are stored encrypted with AES-256-GCM using ENCRYPTION_KEY. See hosted data practices for what opensuitemcp.com keeps and deletes.
Hosted vs self-host
On opensuitemcp.com you can try the same providers. A custom URL has to be reachable from that cloud instance. Pointing at an LLM only on your LAN is a self-host story.