Vera MCP Server

Expose your Vera IT asset data to AI assistants (Claude Desktop, Claude Code) via the Model Context Protocol.

Available Tools

| Tool | Description | | ------------------- | ------------------------------------------------------------------------------- | | get_assets | Search hardware assets — laptops, monitors, phones with owner and warranty info | | get_licenses | Software licenses with vendor, seats, costs, and renewal dates | | get_team | Team members with roles, departments, and primary devices | | get_breach_status | HIBP breach monitoring summary and affected users | | get_tasks | Kanban board tasks with priorities, due dates, and overdue counts |

Quick setup

The easy way — no clone, no build, no JSON editing:

1. In Vera, go to Settings › API Keys and click Generate Key.
2. After generation, pick your Claude client (Desktop or Code) and Copy the prompt shown under "Finish setup in Claude".
3. Paste the prompt into Claude. Claude will add the Vera MCP server to its configuration for you.

That's it. Ask Claude "What assets do we have?" or "Show me upcoming software renewals" to confirm it's working.

Manual setup (power users / non-Claude clients)

For Cursor, Continue, or any other MCP-capable client, wire the server in by hand.

1. Generate an API key

Settings › API Keys › Generate Key in Vera. Copy the key — it's shown once.

2. Configure your client

The server is published to npm, so you don't need to clone this repo. Point your MCP client at npx -y @verait/mcp-server with the two environment variables below.

Claude Code

claude mcp add vera \
  --env VERA_API_URL=https://YOUR_DEPLOYMENT.convex.site \
  --env VERA_API_KEY=vera_k1_YOUR_KEY_HERE \
  -- npx -y @verait/mcp-server

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "vera": {
      "command": "npx",
      "args": ["-y", "@verait/mcp-server"],
      "env": {
        "VERA_API_URL": "https://YOUR_DEPLOYMENT.convex.site",
        "VERA_API_KEY": "vera_k1_YOUR_KEY_HERE"
      }
    }
  }
}

Other MCP clients

Any stdio-transport MCP client works — use npx -y @verait/mcp-server as the command with the same two env vars.

Environment Variables

| Variable | Required | Description | | -------------- | -------- | ---------------------------------------------------------------- | | VERA_API_URL | Yes | Your Convex deployment site URL (e.g. https://xyz.convex.site) | | VERA_API_KEY | Yes | API key generated from Settings › API Keys |

Security

• API keys are hashed (SHA-256) before storage — Vera never stores raw keys.
• All queries are tenant-isolated via the key's associated account.
• Keys can be revoked instantly from Settings › API Keys.
• v1 keys are read-only (read scope only).

Roadmap

• Remote HTTP MCP transport — planned as a Convex httpAction at /mcp so clients can claude mcp add --transport http vera <url> with no local process.

Developing locally

If you're contributing to the MCP server itself:

cd mcp-server
npm install
npm run build      # compiles TypeScript + marks dist/index.js executable
npm link           # makes `vera-mcp-server` available on PATH for local testing