MCP server

VOIX runs a Model Context Protocol server for AI assistants and agents:


https://mcp.voix.tech/mcp

Transport: Streamable HTTP.
Authentication: OAuth. Your client signs you in to VOIX; there is no key or token to copy.
Read-only: the server acts as you, in the workspace you choose, and sees only what you can see. Tools that would change data are not run and answer approval_required.

Connect

Add https://mcp.voix.tech/mcp as a remote MCP server in your client.
Your client opens VOIX in the browser. Sign in if you have not already.
Choose a workspace if you belong to more than one, and select Authorize. VOIX may ask for your passkey first; see OAuth.

To add it to Claude Code:


claude mcp add --transport http voix https://mcp.voix.tech/mcp

Then run /mcp in Claude Code and choose voix to sign in.

Clients that support MCP authorization find everything else through discovery: the server answers 401 with a WWW-Authenticate header pointing to its protected resource metadata , which names https://api.voix.tech as the authorization server. The client identifies itself, and Claude, ChatGPT, VS Code and other well-known clients are recognised automatically through their client ID metadata document. Your client asks for the read and offline_access scopes, so it stays connected. read covers every tool the server offers: calls, contacts, tasks, notes, documents, members and team reports, never more than your role can see. See OAuth for the details.

Disconnect

Open Settings, Apps in the VOIX console and disconnect the client. The connection ends straight away: it cannot refresh, and its current access token expires within 15 minutes. It has to sign in again to reconnect.

Pasted access tokens

Earlier setups sent a VOIX user access token in an Authorization: Bearer <token> header. These still work but are deprecated under the versioning policy. Remove the header and sign in with OAuth instead.

The MCP server does not accept API keys. For server-to-server integrations, use the REST API instead.