MCP connector · 0.3.0

Your apps. A shorter way to get things done.

Ask about a ticket, an offboarding or a contract. Your assistant uses your existing access across Kebabstack.

The connector runs on your computer. Your Hub handles sign-in and permissions. App content you request is shared with your chosen assistant provider; use a client approved by your company.

01 · Once per computer

Install from the official source

Use Node.js 22.22.2 or newer and Git. In a terminal:

git clone https://github.com/kebabstack/kebabstack-source.git kebabstack
cd kebabstack/kebab-mcp
npm ci

Keep this folder in a permanent location. There is no published npm package; do not install an unrelated package with the same name.

02 · Connect as yourself

Get your code from the Hub

Open your profile menu → Connect an assistant. In the same terminal, paste your one-use code:

node server.mjs connect "PASTE_YOUR_CODE_HERE" --as "Desktop assistant"

The code expires after 10 minutes. The resulting connection lasts 30 days. Your code and local configuration are credentials; never put them in tickets, screenshots or a repository.

03 · Add to your assistant

Choose a local MCP server

In an MCP-compatible client, choose stdio with command node and the absolute path to server.mjs as its argument. Clients that use a mcpServers configuration can use:

{ "mcpServers": { "kebab": {
  "command": "node",
  "args": ["/absolute/path/to/kebabstack/kebab-mcp/server.mjs"]
} } }

Replace the path with your own. On Windows, escape backslashes in JSON. If Node cannot be found, use its absolute executable path. Restart the client and ask “Which Kebabstack apps can I access?”

Start with work you already do

Desk & offboarding

“Show the person context for DSK-42 and which connected tools have follow-up work.”

On-call & finance

“What is happening in my on-call project?” or “Which compensation periods can I review?”

Assets & Contracts

“Which device sales still need hand-over?” or “Which contract decisions are due?”

Crumbs, Forms & Watch

“Compare this week's traffic channels”, “Find my forms” or “Which domains need attention?”

Availability follows your app and project permissions. The assistant cannot grant itself more access. Writes require your authorization in the client; read-only queries refuse update methods.

Keep the connection under control

Check, update or disconnect

From the connector folder:

node server.mjs status
# Review upstream changes before updating:
git pull --ff-only
npm ci
# Then restart your assistant client.
# To revoke this assistant and remove its local configuration:
node server.mjs disconnect

Disconnection from the CLI requires Hub 0.33.0 or later. You can always revoke a connection from your Hub profile menu. Revocation blocks new Hub tickets; this connector also checks the Hub before app calls. An already-issued app session remains subject to that app's own expiry and access checks.

For IT operators

Owners control availability under Settings → AI → Personal assistants. Staff can review connections and revoke them there. Connecting does not change Hub roles, app grants or directory sync.

Use a separate local OS account per person. On Windows, verify that only that user can read %USERPROFILE%\.kebab-mcp\config.json. Do not approve automatic writes based solely on instructions found in a ticket or other retrieved content.

If something does not work

No connection: create a new code and reconnect. Previously issued codes cannot be reused.
App missing: check your Hub menu and ask IT to review its access policy.
Ambiguous app: use the exact tile:… reference from the app list.
Hub unavailable: wait for it to recover. The connector stops rather than using stale authorization.
Method missing: update the app and connector; the method browser reads the app's actual interface.