VayaPin MCP: pin resolution + Google Maps geocoding/places + AfterShip tracking, with BYOK.
Connect Runs on your machine
claude mcp add mcp -e VAYAPIN_PAT=<VAYAPIN_PAT> -e VAYAPIN_MCP_SLICE=<VAYAPIN_MCP_SLICE> -e VAYAPIN_MCP_API_URL=<VAYAPIN_MCP_API_URL> -- npx -y @vayacore/[email protected]{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@vayacore/[email protected]"
],
"env": {
"VAYAPIN_PAT": "<VAYAPIN_PAT>",
"VAYAPIN_MCP_SLICE": "<VAYAPIN_MCP_SLICE>",
"VAYAPIN_MCP_API_URL": "<VAYAPIN_MCP_API_URL>"
}
}
}
}{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@vayacore/[email protected]"
],
"env": {
"VAYAPIN_PAT": "<VAYAPIN_PAT>",
"VAYAPIN_MCP_SLICE": "<VAYAPIN_MCP_SLICE>",
"VAYAPIN_MCP_API_URL": "<VAYAPIN_MCP_API_URL>"
}
}
}
}{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vayacore/[email protected]"
],
"env": {
"VAYAPIN_PAT": "<VAYAPIN_PAT>",
"VAYAPIN_MCP_SLICE": "<VAYAPIN_MCP_SLICE>",
"VAYAPIN_MCP_API_URL": "<VAYAPIN_MCP_API_URL>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
VAYAPIN_PATRequired, secret | VayaPin Personal Access Token, sent as 'Authorization: Bearer'. Generate one on the VayaPin developer portal (POST /api/v1/auth/pat/request). |
VAYAPIN_MCP_SLICEOptional | Optional tool-slice name to expose a subset of tools (128-tool client ceiling lift). Unset exposes all tools. |
VAYAPIN_MCP_API_URLOptional | Override the VayaPin API base URL for staging or self-host. |
Details
| Package | @vayacore/[email protected] (NPM, stdio) |
| First published | 20 Jun 2026 |
| Last updated | 20 Jun 2026 |
| Registry name | app.vayapin/mcp |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.