Security

Useful AI, without giving up control.

MCPtoAI is designed so that connecting AI to your computer never means giving it unrestricted access. Here is how your keys, devices and actions are protected.

Security built into every layer.

Your API keys stay on your device

Provider keys are kept in the supported credential store on the device — Keychain on macOS, Windows Credential Manager on Windows, and the supported local credential store on Linux. They are never uploaded to MCPtoAI servers, and requests to AI providers are made from the device.

Every device has its own identity

When you pair a device, it creates a unique Ed25519 signing key that never leaves the device. Each connection is signed and verified, and a captured request cannot be replayed.

Off, Ask or Allow

Every capability and MCP tool has a permission level. With Ask, nothing happens until you approve it in the conversation.

High-impact actions always ask

Writing files, opening applications or links, capturing the screen, camera or microphone, and running commands always require approval. Running commands is turned off by default.

Limited file access

The Device Agent works only inside the folders you allow. Paths are resolved before access, so tricks such as ../ or symbolic links cannot reach other locations.

Protected connections

Traffic between the web app, the hosted relay and your device is protected in transit with TLS. The web app connects to a device with short-lived tickets that only its owner can obtain. MCPtoAI does not currently provide end-to-end encryption, so chat traffic passes through the hosted relay while it is being delivered.

Safe MCP connections.

MCP servers extend what AI can do, so they follow the same principles as the rest of MCPtoAI.

Learn about MCP

  • Remote MCP servers must use HTTPS
  • Private and local network addresses are blocked for remote servers
  • Local MCP programs can only be added on the device, never from the web
  • Sign-in tokens and server secrets are stored on your device

What is stored where.

A clear account of where your information lives.

Stored by MCPtoAI

  • Your account details
  • Your paired devices and their public keys
  • Conversation history, only if you choose MCPtoAI Cloud history

Stays on your device

  • AI provider API keys
  • The device's private signing key
  • MCP sign-in tokens and server secrets
  • Your permission settings and files
  • Conversation history when you choose This device only

Shared with services you choose

  • Your messages go to the AI provider you select
  • Tool calls go to the MCP services you connect

Security questions

Does MCPtoAI store my API keys?

No. Your keys stay in your operating system's credential store on your device. MCPtoAI's servers never receive them.

Can the AI do something without my knowledge?

Only actions permitted by your device policy can run. Capabilities set to Ask wait for your approval, and high-impact actions are forced to ask even if a local setting would otherwise allow automatic use.

How do I remove a device's access?

Remove or disconnect the device from MCPtoAI. The server rejects a removed device if it tries to reconnect, and the device must be paired again before it can return. Clearing local MCPtoAI data also removes stored provider keys, MCP credentials and the local device identity.

Stay in control of your AI.

Install MCPtoAI on your platform and decide exactly what AI may do on your computer.

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.

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