Connect Veqtor to Claude.

Before you start

What you need

• A Mac or Linux computer.
• Claude Code on Mac or Linux, or Claude Desktop on a Mac.
• uv installed so Veqtor can run in an isolated Python environment.

Option A

Claude Code on Mac or Linux

Register the exact public release for your user account:

claude mcp add --transport stdio --scope user veqtor -- uvx veqtor-mcp@0.1.2

Then confirm that Claude Code can see the registration:

claude mcp get veqtor

Open a new Claude Code session after registering Veqtor. The user scope keeps this private local connection available across your projects on this computer. It does not make Veqtor a network service.

Set the author shown in new tracked changes

If you want Word to show your name as the author of new changes, register the server with this environment setting. Replace Your Name with your actual name:

claude mcp add --transport stdio --scope user veqtor \
  -e VEQTOR_TRACKED_CHANGE_AUTHOR="Your Name" -- \
  uvx veqtor-mcp@0.1.2

If you do not set a name, Word will show Veqtor MCP. The author is fixed when the server starts and Claude cannot change it for an individual edit.

Option B

Claude Desktop on a Mac

Desktop apps may not see the same terminal paths as your shell. First find the full path to uvx:

command -v uvx

In Claude Desktop, open Settings → Developer → Edit Config. This opens ~/Library/Application Support/Claude/claude_desktop_config.json.

If your file already contains mcpServers

Add only the veqtor entry inside the existing mcpServers object. Keep every other server and every setting outside that object. JSON entries next to each other need a comma between them.

"veqtor": {
  "command": "/absolute/path/to/uvx",
  "args": ["veqtor-mcp@0.1.2"]
}

If the file has other settings but no mcpServers

Add this property inside the file's outermost braces, alongside the existing root-level settings. Keep those settings and add a comma between adjacent root properties.

"mcpServers": {
  "veqtor": {
    "command": "/absolute/path/to/uvx",
    "args": ["veqtor-mcp@0.1.2"]
  }
}

If the file is empty

Use this complete configuration. In either example, replace /absolute/path/to/uvx with the result from command -v uvx.

{
  "mcpServers": {
    "veqtor": {
      "command": "/absolute/path/to/uvx",
      "args": ["veqtor-mcp@0.1.2"]
    }
  }
}

Choose the author shown in new tracked changes

The examples above use the default author, Veqtor MCP. To show your own name in Word, add this env setting inside the veqtor entry, after the args line. Add a comma after the args line, and replace Alex Morgan with your actual name. Do not leave the example name in your configuration.

"env": {
  "VEQTOR_TRACKED_CHANGE_AUTHOR": "Alex Morgan"
}

Quit Claude Desktop fully and reopen it after changing the executable, version or author name.

Confirm the Claude Desktop connection

Start a new chat, click the + button beside the message box, then open Connectors. Veqtor should appear with its tools. You can also open Settings → Developer to see its connection status and logs. The claude mcp get veqtor command checks Claude Code only; it does not verify this Desktop configuration.

First run

Verify the connection with sample documents

Create a fresh, disposable four-round negotiation:

uvx --from "veqtor-mcp==0.1.2" veqtor-demo-rounds ~/veqtor-demo-rounds

In a new Claude session, ask:

Using the Veqtor tools, what happened to the limitation of liability across the rounds in ~/veqtor-demo-rounds?

If Claude identifies and explains the four rounds, the connection is working. Continue with the recorded demo before trying a write workflow.

Troubleshooting

Common setup problems

Claude Code does not show Veqtor

Run claude mcp get veqtor in Terminal. If the registration appears, close the current Claude Code session and start a new one.

Claude Desktop does not show Veqtor

Fully quit and reopen Claude Desktop, then check + → Connectors in a new chat. Open Settings → Developer to check the connection status and server logs. Do not use claude mcp get veqtor for this check; it reads Claude Code registrations, not claude_desktop_config.json.

Claude Desktop stopped showing another server

Restore your backup, then add only the veqtor entry inside its existing mcpServers object. Preserve all other entries and root-level settings, and check the commas between JSON entries.

Claude Desktop cannot start the server

Use the absolute path returned by command -v uvx. Do not assume the desktop app inherits your shell path.

Run local diagnostics

uvx veqtor-mcp@0.1.2 doctor

Still blocked?

Search or open a GitHub Issue using synthetic files only. Never post client wording, local paths, credentials or local activity records.