ubcab-bo-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
ubcab-bo-mcp
MCP server for the UBCab Backoffice (registration-bo) API — the same backend
that powers operator.ubcab.mn. Lets Claude search drivers, read driver detail
and rating, change driver state, and list service options.
Built on the same pattern as timely-mcp: a single self-contained
api/index.ts (the Vercel serverless function) that runs over Streamable HTTP
on Vercel (bearer + OAuth 2.1 PKCE) or over stdio locally.
Live endpoint: https://bo-mcp.vercel.app/mcp (POST, Bearer auth). Verified: GET /health → {"status":"ok"}.
Auth
The BO uses Keycloak SSO (realm ubcab-bo). Since 2026-11-02 people log in
with Microsoft SSO and the realm rejects the password grant on every client
(unauthorized_client «Client not allowed for direct access grants»), so the old
username/password + TOTP login is gone. The server gets an access token from
https://sso.ubcabtech.com/realms/ubcab-bo/protocol/openid-connect/token:
client_credentials (service account) — set
UBCAB_BO_CLIENT_ID+UBCAB_BO_CLIENT_SECRETof a confidential client with Service accounts enabled, created by the BO team with the roles the tools need. Durable: no user, no 2FA, every serverless instance logs in on its own.refresh_token grant — set
UBCAB_BO_REFRESH_TOKEN(e.g. an offline token from a one-time browser login). When a client secret is set too, it is sent with the refresh, and a rejected refresh token falls back to client_credentials.
Express reads its own client: UBCAB_EXPRESS_CLIENT_ID + _CLIENT_SECRET (operator-api; set the
same values if the BO team issues one client for everything). Marketing (marketing-bo-api and the
image upload) and UBEats (ubeats_* tools, ubeats-bo-api) reuse the UBCAB_BO_* client unless
UBCAB_MARKETING_CLIENT_ID / UBEATS_CLIENT_ID (+ _CLIENT_SECRET) is set — the shared client
then needs their roles and origins too. Each also accepts *_REFRESH_TOKEN. The public BO clients
(ubcab-registration-bo, express-bo, ubeats-bo, ubcab-marketing-bo) cannot have service accounts.
Access tokens are short-lived (~5 min); the server caches and silently re-auths.
Every API call also sends Origin/Referer (operator.ubcab.mn, office.ubcabexpress.mn,
office.ubeats.mn) — ask the BO team to put that origin in the service-account client's
Web origins (Keycloak copies them into the token's allowed-origins; anything else gets
403 «Invalid origin», verified for UBEats on 2026-10-16).
A rejected token request is returned to the tool caller and logged as Keycloak auth failed (HTTP <status>) [build …, client=…, origin=…, grant=…, creds=…] (the log line adds Keycloak's
error code) — the only trace in the Vercel logs, because tool errors return HTTP 200.
Related MCP server: uptime-kuma-mcp-server
Per-user BO token (X-BO-User-Token)
A caller that is already authenticated to this server (bearer token or the built-in OAuth) can
forward the signed-in person's own BO access token in the request header
X-BO-User-Token: <access token (JWT)>. Then:
The registration and marketing tools call BO with
Authorization: Bearer <that token>, so every action runs with the person's own permissions and shows their name in BO's audit log. No Keycloak request is made, and the token is never cached or shared: it exists only for the duration of that one HTTP request.Express and UBEats tools ignore the header and keep their own credentials.
Origin/Refererfor these calls come fromUBCAB_BO_USER_ORIGIN(defaulthttps://operator.ubcab.mn), read on every request; the auth-context suffix shows the same origin.ubcab_marketing_upload_imageuses the same token and origin (it never falls back to the server credentials when the header is present).If BO answers 401, there is no retry and no fallback to the server credentials; the tool error starts with
BO_USER_TOKEN_REJECTED (HTTP 401)(login expired: the caller should get a fresh token and retry once). If BO answers 403, the error starts withBO_USER_FORBIDDEN (HTTP 403): the person is signed in but lacks permission, so a fresh token will not help; no retry, no fallback.A header that is longer than 16 KB or not three base64url segments gives a tool error starting with
BO_USER_TOKEN_INVALIDand no BO call. The header is ignored on requests that fail the server's own authentication.Without the header nothing changes: the server's own credentials are used.
The token is never logged or echoed: JWT-looking strings and the exact header value are replaced with
***in errors and logs. Auth errors end withuser_token=yes|no.
Tools
Tool | Method / Endpoint | Purpose |
|
| Жолоочийг утас/регистр/нэр/shortId-аар хайх → |
|
| Жолоочийн дэлгэрэнгүй (profile, vehicle, kyc…) |
|
| Жолоочийн үнэлгээ |
|
| Төлөв солих: |
|
| Үйлчилгээний сонголтын жагсаалт |
|
| Жолоочийн үйлчилгээний түүх; |
|
| Хэтэвчний үлдэгдэл |
|
| Хэтэвчний гүйлгээний түүх (paged; |
|
| Тээврийн хэрэгслүүд |
|
| ⚠ Машины үйлчилгээ нэмэх/хасах ( |
|
| Сэтгэгдэл/үнэлгээний жагсаалт (paged) |
|
| Цолны түүх (paged) |
|
| Audit log — хэн юуг хэзээ өөрчилсөн ( |
|
| Техникийн үзлэгийн дэлгэрэнгүй (асуулт бүрийн хариу, result, expiresAt) |
|
| Үзлэгт хамаарах жолоочид (paged) |
|
| Хэрэглэгч (rider) хайх (body: filter.query) |
|
| Хэрэглэгчийн аяллын түүх; |
|
| Аяллын үндсэн бүх мэдээлэл |
|
| Маршрут (GPS зам) |
|
| Нэхэмжлэл |
|
| Хэрэглэгчийн нэхэмжлэхүүд (filter.status, ж: open) |
|
| Нэхэмжлэхийн дэлгэрэнгүй |
|
| Аль ч үйлчилгээний аяллын нэхэмжлэх |
|
| Төлбөр тооцооны задаргаа |
|
| Гомдол |
|
| Торгууль (жагсаалт) |
|
| ⚠ Торгууль цуцлах (write) |
|
| ⚠ Хүргэлтийн торгууль цуцлах |
|
| Урамшуулал |
|
| TEMU/чиглэлийн илгээмж хянах (нэвтрэлтгүй нийтийн API) |
|
| UBExpress энгийн захиалга хайх (operator, client express-bo) |
|
| UBExpress буцах захиалга хайх |
|
| Гарын авлагын категорууд |
|
| ⚠ Шинэ категор нэмэх (name, order) |
|
| Категорын дэлгэрэнгүй |
|
| ⚠ Категор устгах |
|
| Формын meta |
|
| Мэдээний (Press) ангиллууд |
|
| ⚠ Шинэ мэдээний ангилал |
|
| Ангилалын дэлгэрэнгүй |
|
| ⚠ Засах |
|
| Тусламжийн агуулгууд (filter: slug, title) |
|
| ⚠ Агуулга нэмэх ( |
|
| Агуулгын дэлгэрэнгүй |
|
| ⚠ Агуулга засах |
|
| ⚠ Агуулга устгах |
|
| Формын meta |
|
| Бүлгийн сонголт ( |
|
| Хэлний сонголт |
|
| Press контентууд |
|
| ⚠ Контент нэмэх (title, cover, category, preview) |
|
| Дэлгэрэнгүй |
|
| ⚠ Засах |
|
| ⚠ Устгах |
|
| Формын meta |
|
| Ангиллын сонголт ( |
|
| Зураг байршуулах → |
|
| ⚠ Устгах |
|
| Формын meta (талбар динамик) |
|
| UBEats Cloud Kitchen захиалга хайх (filter.customerPhone) |
|
| Cloud Kitchen захиалгын бүрэн дэлгэрэнгүй |
|
| Cloud Kitchen төлөвийн түүх |
|
| UBEats Merchant захиалга хайх |
|
| Merchant захиалгын бүрэн дэлгэрэнгүй |
|
| Merchant төлөвийн түүх |
⚠
driver_get/trip_getreturn PII (name, phone, register no, civil ID).driver_set_stateis a write action.
Local run (stdio)
npm install
npm test # offline auth tests (compiles first; fetch is stubbed)
cp .env.example .env # fill UBCAB_BO_CLIENT_ID + UBCAB_BO_CLIENT_SECRET (+ the express pair)
npm run test:login # live: one read-only call per configured API, prints status/row counts onlyClaude Desktop config:
{
"mcpServers": {
"ubcab-bo": {
"command": "node",
"args": ["/abs/path/to/ubcab-bo-mcp/dist/api/index.js"],
"env": {
"UBCAB_BO_CLIENT_ID": "...",
"UBCAB_BO_CLIENT_SECRET": "..."
}
}
}
}Deploy (Vercel)
Deploy with the Vercel CLI from this folder: vercel --prod (.vercel/project.json
links it to ubc-ab/bo-mcp). Pushes to GitHub (naranmunkh/bo-mcp, a public repo)
stopped auto-deploying after the project moved to the UBCab team.
Zero-config: api/index.ts is auto-built as a serverless function, and
vercel.json rewrites send every path (/mcp, /health, /.well-known/*) to
it. There is intentionally no build script — a build script makes Vercel
expect a static public/ output and the deploy fails. Local TypeScript build is
npm run compile.
Required env vars on the Vercel project: UBCAB_BO_CLIENT_ID, UBCAB_BO_CLIENT_SECRET
(Sensitive), and UBCAB_BO_MCP_AUTH_TOKEN (openssl rand -hex 32); for the express tools also
UBCAB_EXPRESS_CLIENT_ID + _CLIENT_SECRET (marketing and UBEats use the BO client unless given their own).
The retired *_USERNAME, *_PASSWORD and *_TOTP_SECRET vars are ignored — delete them.
Connect from Claude with Authorization: Bearer <UBCAB_BO_MCP_AUTH_TOKEN> at
https://bo-mcp.vercel.app/mcp. The endpoint fails closed if
UBCAB_BO_MCP_AUTH_TOKEN is unset.
Is the latest build live?
Every Keycloak auth error ends with a non-secret context, for example
[build 2026-11-02 client-credentials, client=bo-mcp-registration, origin=https://operator.ubcab.mn, grant=client_credentials, creds=UBCAB_BO_*].
No [build …], or an older build (2026-10-16 bo-login+totp) → an old deploy is
still serving: the top Production deployment in Vercel must be the latest code
("Redeploy" on an old deployment rebuilds that old source). client / origin /
creds show what was actually sent and which env vars it came from, so a stale
override is visible there.
Extending
Add a new endpoint by registering another tool inside createMcpServer() in
api/index.ts — copy one of the existing reg(...) blocks.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server exposing klokin time-tracking operations (employees, time entries, stores) to AI clients.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server for Sendbird — chat users, channels, members, and messages from your AI client.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions12MIT
- FlicenseBqualityBmaintenanceMCP server for managing self-hosted Uptime Kuma monitors and querying uptime statistics from Claude.15-
- FlicenseNot gradedqualityCmaintenanceA local MCP server that connects the Globick activities API to Claude Desktop, enabling natural language search and filtering of the activities catalogue.-

Upvote Club Remote MCPofficial
AlicenseNot gradedqualityCmaintenanceRemote MCP server for Claude.ai to interact with Upvote Club's API, enabling task creation, status checking, and platform listing via natural language.42MIT