Vantage Movers MCP

Remote Model Context Protocol server so agents can use the Granot / Vantage backend and query MongoDB Atlas from one place.

Hosted on Vercel with mcp-handler v2 and Next.js. That is the current Vercel-supported path: Streamable HTTP plus the 2026-07-28 MCP spec, no Redis, no long-lived stdio process.

Why this library

Related MCP server: MongoDB MCP Server

Required MCP configuration

VANTAGE_API_SECRET is required in the client config. The server puts that value on the x-api-secret header when it calls https://vantage-movers-main-server.vercel.app.

Cursor / Claude-style Streamable HTTP:

{
  "mcpServers": {
    "vantage-movers": {
      "url": "https://vantage-movers-mcp.vercel.app/api/mcp",
      "headers": {
        "Authorization": "Bearer <VANTAGE_API_SECRET>"
      }
    }
  }
}

x-api-secret is accepted as well if a client prefers the Vantage header name:

{
  "mcpServers": {
    "vantage-movers": {
      "url": "https://vantage-movers-mcp.vercel.app/api/mcp",
      "headers": {
        "x-api-secret": "<VANTAGE_API_SECRET>"
      }
    }
  }
}

Do not put the secret in env for a remote URL. HTTP MCP clients only send headers. env is for local stdio servers.

Production also stores VANTAGE_API_SECRET on the Vercel project so a public URL cannot open Mongo with a made-up token. The client value must match.

MongoDB

The official MongoDB MCP server is stdio. This deployment keeps a dedicated Mongo surface in-process:

• mongo_list_databases

• mongo_list_collections

• mongo_collection_schema

• mongo_collection_indexes

• mongo_find

• mongo_aggregate

• mongo_count

• mongo_db_stats

Read-only. $out and $merge are rejected. Default database is vantagemovers (or testvantagemovers when TEST_MODE=true).

Use lead tools for Form / Call Lead writes. Raw Mongo mutations would skip Sheet Sync and CRM posting.

First tool slice

History tools (read-only)

The general endpoint also exposes read-only history tools backed by the main server's GET /api/v1/internal/sales-intelligence/history/* routes (authenticated with the same x-api-secret; never raw Mongo). The server answers 404 on them while its SALES_INTELLIGENCE_ENABLED flag is off, and refuses the retired Sales Intelligence scoped key. They return canonical records and provider metadata: names, E.164 numbers, job numbers, attachments, entity changes, Granot observations, bookings and message metadata. They never return call analyses, conversations, Move assessments, Outreach records, transcript text, Lead Message bodies or emails.

The server-slimming release (2026-10) retired the AI analysis tools list_analyses, get_analysis, get_conversation, get_move_assessment, get_prior_analyses and get_subject_story, and the scoped /api/intelligence-mcp endpoint with its envelope schema and analysis prompt. The main server removes their routes in the same release. This build only calls the three retained routes, which exist before and after that server change, so it can deploy first.

Later slices: Granot syncs, Owner Registry items, booking cases.

Local

pnpm install
cp .env.example .env.local
# fill VANTAGE_API_SECRET and MONGO_URI
pnpm test
pnpm typecheck
pnpm dev

MCP URL locally: http://localhost:3100/api/mcp

Deploy

Production is Vercel CLI only. The project is not Git-connected. Agents follow .agents/skills/deploy-vantage-movers-mcp/SKILL.md.

npx --yes vercel --prod --yes --scope vantage-4d3db9ef

Environment