Model Context Protocol

Connect Vektor to your AI assistant

The Vektor MCP server gives Claude, Codex, and any other MCP-compatible assistant secure access to your TMS — read-only by default. Ask about your operations in plain language and get answers from your live data.

https://mcp.vektortms.dev/mcp

Connect a client Manage in Vektor

Read-only by default OAuth 2.1 secured Per-company access

How it works

Three steps, about a minute. Your assistant never sees your password — sign-in and approval stay in Vektor.

Add the endpoint

Paste the MCP endpoint URL above into your assistant as a remote MCP server or custom connector.

Sign in to Vektor

Your browser opens Vektor. Sign in as usual if you are not already; the assistant never sees your password and only ever receives an access token.

Approve the connection

Vektor shows which company you are connecting and exactly what the assistant will be able to read. Approve, and you are sent straight back to the assistant.

Connect your client

Pick your assistant below. Any client that supports remote MCP over streamable HTTP with OAuth works the same way.

Claude — web & desktop

Add Vektor as a custom connector. Works on every Claude plan.

Open Settings → Connectors.
Click Add custom connector.
Name it Vektor and paste the endpoint URL https://mcp.vektortms.dev/mcp.
Click Add, then Authorize — approve the connection in Vektor.

Claude Code (CLI)

claude mcp add --transport http vektor https://mcp.vektortms.dev/mcp

Then run /mcp inside Claude Code and click Authorize to approve the connection in your browser.

Codex CLI

Add the server, then run the built-in OAuth login.

codex mcp add vektor --url https://mcp.vektortms.dev/mcp
codex mcp login vektor

codex mcp login opens your browser to approve the connection in Vektor.

Or via ~/.codex/config.toml

[mcp_servers.vektor]
url = "https://mcp.vektortms.dev/mcp"

Then run codex mcp login vektor.

What you get

Built for safe, auditable access to your operational data.

Ask in plain language

Query and summarize your live TMS data through natural conversation — no dashboards, no exports.

Read-only by default

A new connection is given read-only tools and nothing else. Writing is a deliberate opt-in on that one connection, and destructive or outbound actions need a second one — so nothing in your account changes unless you turned it on.

Scoped to one company

You approve the connection inside one company, and access stays bound to that company for the life of the connection.

Every call audited

Each tool call is recorded against your user and connection. Revoke access anytime from MCP settings in Vektor.