> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voxworks.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting an Assistant

> Add the Voxworks MCP server to Claude or another MCP-capable assistant, then approve the connection on the Voxworks authorisation screen.

## Server address

Add Voxworks to your assistant as a remote MCP server (sometimes called a custom connector) with this address:

```text theme={null}
https://mcp.voxworks.ai/mcp
```

There is no API key to copy. The first time the assistant connects, it sends you to Voxworks to sign in and approve the connection.

***

## Adding it to your assistant

Any assistant that supports remote MCP servers with sign-in can connect. The exact steps depend on the assistant:

* **Claude (web and desktop):** add a custom connector and paste the server address. Claude then opens the Voxworks sign-in when you first connect.
* **Claude Code:** run the command below, then run `/mcp` inside Claude Code and choose **voxworks** to sign in.

```bash theme={null}
claude mcp add --transport http voxworks https://mcp.voxworks.ai/mcp
```

* **Other assistants:** look for an option to add a remote MCP server or connector by URL, and use the address above.

***

## Approving the connection

### Authorising the app

After you sign in to Voxworks you see a screen headed **Authorize `{clientName}`**, which explains that "`{clientName}` is requesting access to your Voxworks team. It can only do what you allow below.", then lists under **This will allow it to:** what the assistant is asking for. Only the permissions the assistant requests are shown. [Permissions](/mcp/permissions) explains each one.

### Picking a team

Below that is a **Team** picker — "The client will act within this team's data." Pick the team the assistant should work in. If you belong to only one team, the screen names it instead. Then choose **Approve** or **Deny**.

<Tip>
  To try things out, approve the connection for a test team first. The assistant can only work in the team you pick, so to switch teams, revoke it and connect again.
</Tip>

### If something goes wrong

You will see one of three outcome pages:

* **Could not connect** — "Connecting an AI assistant to Voxworks needs an account that belongs to a team. Ask a team owner to invite you, then try connecting again."
* **Authorization cancelled** — you chose **Deny**.
* **Authorization error** — the request could not be completed; start again from the assistant.

***

## Staying connected

If you approved **Stay connected without re-approving**, the assistant stays connected and you won't be asked again each time you use it. Without it, you approve the connection again when its access runs out.

When Voxworks adds a new permission, assistants connected before it was added don't get it automatically. Remove Voxworks from the assistant and add it again to see the new permission on the authorisation screen.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.