Other MCP clients

How-to guide

Any MCP client that can launch a local server over stdio can use the tool. There are two ways to register it: a JSON snippet you paste yourself, or the install-mcp command that edits the client’s configuration file for you.

Option A: paste a snippet (nothing to install)

The snippet runs the published npm package through npx, so the client fetches the latest version at every start and nothing has to be installed beforehand. Node.js 20 or newer must be on the machine.

Claude Code

claude mcp add --scope user xflow-timesheet -- npx -y sap-fiori-timesheet-mcp@latest

or add this to ~/.claude.json:

{
  "mcpServers": {
    "xflow-timesheet": { "command": "npx", "args": ["-y", "sap-fiori-timesheet-mcp@latest"] }
  }
}

Claude Desktop

Prefer the one-click .mcpb install. Otherwise add this to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{
  "mcpServers": {
    "xflow-timesheet": { "command": "npx", "args": ["-y", "sap-fiori-timesheet-mcp@latest"] }
  }
}

Cursor

Add this to ~/.cursor/mcp.json, then enable the server under Settings → MCP:

{
  "mcpServers": {
    "xflow-timesheet": { "command": "npx", "args": ["-y", "sap-fiori-timesheet-mcp@latest"] }
  }
}

VS Code

VS Code uses a servers map with a type. Add this to the user mcp.json (macOS: ~/Library/Application Support/Code/User/mcp.json, Windows: %APPDATA%\Code\User\mcp.json, Linux: ~/.config/Code/User/mcp.json):

{
  "servers": {
    "xflow-timesheet": { "type": "stdio", "command": "npx", "args": ["-y", "sap-fiori-timesheet-mcp@latest"] }
  }
}

Restart the client afterwards. Working against another SAP system? Add an env block to the entry:

"env": { "XFLOW_LAUNCHPAD_URL": "https://your-fiori-host.example/sap/bc/ui2/flp#Shell-home" }

All variables are listed in the configuration reference.

Option B: let the CLI write the configuration

If you have installed the CLI, one command registers the server and keeps a .bak copy of the file it edits:

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

Useful flags:

Flag	Effect
--npx	Write an npx-based entry (as in option A) instead of pointing at the locally installed binary.
--print	Print the JSON snippet instead of writing it.
--config-path <file>	Write to this file instead of the client’s default location, for example a project-level .mcp.json.
--session-file-env	Pin XFLOW_SESSION_FILE in the entry to the current session path.

Without --npx the entry points at the xflow-timesheet-mcp binary on your PATH (or at node <checkout>/bin/xflow-timesheet-mcp.js when run from a repository checkout). That avoids the npx start-up cost and lets you patch the tool locally.

Check the result at any time:

xflow-timesheet doctor

It reports Node, the stored session, the browser profile and, for each supported client, whether the server is registered.

Where the clients keep their configuration

Client	File
Claude Code	~/.claude.json
Claude Desktop	macOS ~/Library/Application Support/Claude/claude_desktop_config.json; Windows %APPDATA%\Claude\claude_desktop_config.json; Linux ~/.config/Claude/claude_desktop_config.json
Cursor	~/.cursor/mcp.json
VS Code	macOS ~/Library/Application Support/Code/User/mcp.json; Windows %APPDATA%\Code\User\mcp.json; Linux ~/.config/Code/User/mcp.json

Note

The server’s binary is published under two names: sap-fiori-timesheet-mcp (so npx sap-fiori-timesheet-mcp starts the server directly) and xflow-timesheet-mcp (the same launcher, for local installs). The CLI is xflow-timesheet.

First sign-in from an assistant

Ask the assistant to sign you in; it calls sso_login, which opens a browser window on your machine for you to sign in. Details and variants are in Sign in, renew and sign out.