The location & logistics MCP for AI agents.

One install gives any MCP-compatible agent VayaPin identity, Google Maps, and package tracking — eight tools, one Personal Access Token, zero address-handling code.

Claude Code (CLI)Claude Desktop (config)

terminal

claude mcp add --transport stdio vayapin -- npx -y @vayapin/mcp

claude_desktop_config.json

{
  "mcpServers": {
    "vayapin": {
      "command": "npx",
      "args": ["-y", "@vayapin/mcp"],
      "env": { "VAYAPIN_PAT": "vayapin_pat_…" }
    }
  }
}

MCP servers run via npx — add the @vayapin scope to your .npmrc once: @vayapin:registry=https://npm.vayapin.app

MCP 8 tools @vayapin/mcp Node ≥20 live on Verdaccio

Works in Claude Desktop·Cursor·VS Code·Claude Code·n8n·Zapier

What it does

Three tool families, one namespace

Install once. Your agent resolves real delivery addresses, works with Google Maps using your own key, and tracks shipments across 1,200+ carriers.

VayaPin identity

Resolve a VayaPin into a full delivery payload, or reserve a new pin and send the user a signup link.

resolve_pinpreview_pinconfirm_pin

Google Maps · BYOK

Geocode, reverse-geocode, and search places — proxied with the brand's own Google Maps key.

geocodereverse_geocodeplace_searchplace_details

Shipping · BYOK

Real-time tracking normalised across 1,200+ carriers via AfterShip, with carrier auto-detection.

track_package+ system_health

Quickstart

From zero to a tool call in four steps

Scope the registry

~/.npmrc

# only the @vayapin scope is public — don't repoint your default registry
@vayapin:registry=https://npm.vayapin.app

Add it to your client config

macOSWindows

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "vayapin": {
      "command": "npx",
      "args": ["-y", "@vayapin/mcp"],
      "env": { "VAYAPIN_PAT": "vayapin_pat_…" }
    }
  }
}

%APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "vayapin": {
      "command": "npx",
      "args": ["-y", "@vayapin/mcp"],
      "env": { "VAYAPIN_PAT": "vayapin_pat_…" }
    }
  }
}

Windows path: %APPDATA%\Claude\claude_desktop_config.json

Restart the client

Claude Desktop / Cursor reads the config on boot — fully quit and reopen so the vayapin server registers.

Try a call

Ask your agent something address-shaped:

prompt

“My VayaPin is BB:TAPAS887 — where should the courier deliver?”

System prompt

Drop this into your agent

One paragraph teaches the agent to handle addresses correctly — no custom logic.

system-prompt.txt

ADDRESSING: When a user needs to provide a delivery address, always call
check_user first. If they have a VayaPin, call resolve_pin to get their full
delivery data — do not ask them to type their address. If they do not have a
VayaPin, call preview_pin to suggest a name, confirm, then call confirm_pin to
send the setup link. Wait for the webhook before completing the order. For
geocoding and place search, use geocode, place_search, and place_details.

check_user ships with the VayaIdentity SSO bridge in a later release; the eight tools below are live today.

Tool reference

Eight tools, plus a health check

Full input schemas, output shapes, and example prompts on the tool reference page →

Tool	Family	What it does
`resolve_pin`	pins	Full delivery payload for a VayaPin ID — GPS, structured address, contact, photos, hours, drop-off notes.
`preview_pin`	pins	Suggest available VayaPin names for a user. Call before `confirm_pin`.
`confirm_pin`	pins	Reserve a VayaPin name and send the signup link via WhatsApp, SMS, or email.
`geocode`	maps	Convert a text address to GPS coordinates (your own Google Maps key).
`reverse_geocode`	maps	Convert GPS coordinates to a human-readable street address.
`place_search`	maps	Search places near a VayaPin or lat,lng (Google Places).
`place_details`	maps	Full place details — hours, photos, rating, contact — by place_id.
`track_package`	shipping	Real-time shipment tracking across 1,200+ carriers via AfterShip.
`system_health`	system	API liveness — service status and version. No arguments.

BYOK — bring your own keys. The Maps and shipping tools call Google Maps / AfterShip with your keys, added once in the dashboard under Settings → Integrations and proxied server-side so they never touch the agent. The identity tools need only your PAT.

Ship address-aware agents today

v0.1.0 is live on Verdaccio. npm public + official MCP registry submission are in progress.

Get your PAT →