Install the CLI

How-to guide

Prerequisite: Node.js 20 or newer (node --version). Nothing else. The headless browser used for signing in is downloaded automatically the first time you sign in.

npx (no install)

Run any command through the published package:

npx -y -p sap-fiori-timesheet-mcp xflow-timesheet sso
npx -y -p sap-fiori-timesheet-mcp xflow-timesheet std days

Good for trying it out; a little slower to start, and you keep the long prefix.

Clone and link (recommended)

git clone https://github.com/arno-vel-bept/sap-fiori-timesheet-mcp.git
cd sap-fiori-timesheet-mcp
npm install && npm run build     # or: pnpm install && pnpm build
npm link                         # puts xflow-timesheet and xflow-timesheet-mcp on your PATH

Two commands, easy to update with git pull && npm run build, and easy to patch.

Tarball

Hand someone a single file:

npm run build && npm pack        # on your machine → sap-fiori-timesheet-mcp-<version>.tgz
npm install -g sap-fiori-timesheet-mcp-<version>.tgz   # on the target machine

Why not npm install -g git+https://…

npm’s global install of a git dependency has a known issue (npm/cli#2919 and related reports) where the installed package ends up as a dangling symlink into a temporary directory that npm deletes right after. Clone and npm link is the reliable path and takes the same two commands.

Then, once

xflow-timesheet sso              # sign in once in a real browser window
xflow-timesheet doctor           # checks Node, session, browser profile and MCP registrations

Optionally register the MCP server for your editor from the same install:

xflow-timesheet install-mcp --client claude-code     # or: claude-desktop | cursor | vscode

See Other MCP clients for what that writes and where.

What gets created on your machine

Path	Content
~/.config/xflow-timesheet/session.json	The SAP session cookies (file mode 0600).
~/.config/xflow-timesheet/profile/	A dedicated browser profile that remembers your identity-provider sign-in (mode 0700).
Playwright’s browser cache (for example ~/Library/Caches/ms-playwright on macOS)	The Chromium build used for signing in, shared by every install on the machine.

Both locations can be moved with environment variables; see the configuration reference. Why these two files exist and what they mean for security is explained in How authentication works.