AI models

One conversation. Your choice of model.

Use the provider that suits the task — and switch without starting over when a model reaches its limit.

Hit a limit? Keep going.

Usage limits, outages and new releases are part of working with AI. In MCPtoAI, your conversation is at the centre of your work — not the provider.

Choose another supported model from the model menu and carry on. The available conversation context is passed to the model you select so it can pick up where the previous one stopped. Your history-storage choice does not change: Cloud history stays in MCPtoAI Cloud, while device-only history stays on the selected device.

Supported AI providers.

Use your own key for cloud providers, or run models on your own computer.

Cloud providers

  • OpenAI
  • Anthropic
  • DeepSeek
  • xAI (Grok)
  • Moonshot (Kimi)
  • Mistral AI
  • Groq
  • Cerebras
  • Together AI
  • Fireworks AI
  • OpenRouter
  • NVIDIA NIM
  • Replicate
  • EVREN

Local and custom

  • Ollama
  • LM Studio
  • Any OpenAI-compatible server

Available models depend on your provider account. Capabilities such as tool use and image input vary from model to model.

Choose the right model for each step.

Strengths differ

Use one model for analysis and another for writing code — within the same conversation.

Cloud or local

Use a local model when you want model inference to run on your own computer, and use cloud models when you need their capabilities. Relay and history behavior still follows the MCPtoAI connection and history settings you chose.

Your keys, your billing

You use your own provider accounts. Usage is billed by the provider, under your account.

Questions about models

Do I lose context when I switch models?

Usually not. MCPtoAI passes the available conversation context to the model you select. Models have different context sizes and tool capabilities, so a very long conversation or a tool-heavy workflow may not fit every model in exactly the same way.

Can I use local models?

Yes. MCPtoAI works with Ollama, LM Studio and other OpenAI-compatible servers running on your computer. Local models do not need an API key.

Who pays for model usage?

You do, directly to the provider. MCPtoAI uses the keys you add, so usage appears on your own provider account.

Stop starting over.

Keep your work in one conversation and switch among the supported models that fit the moment.

Explore what MCPtoAI can do

A practical AI workspace, not just a chat window. Connect your computer, supported AI providers and external tools; keep control of the actions they take.

Choose the model for the task

Use supported cloud providers or local models, switch within a conversation and retain the available context. Model capabilities and limits vary.

Stay in control

Configure Off, Ask or Allow for individual tools. Provider credentials remain on the device; remote services receive data needed for approved requests.

Understand where data goes

Web messages pass through the hosted TLS relay; this is not end-to-end encryption. Choose cloud or device-only history, and review third-party tool and Skill risks.

Explore Skills