Customer MCP Router for Linux

Connect each customer's Glide organization once, then use that saved connection from Claude Code and Codex. The router links a local project folder to one customer and checks the organization before allowing tool calls.

This repository contains the Linux version. The macOS version is mcp-customer-router-macos.

Install

Requirements: Linux with a systemd user session, Node.js 22.12 or newer, curl or wget, tar, and sha256sum.

curl -fsSLO https://github.com/evanfurniss-dev/mcp-customer-router-linux/releases/latest/download/install.sh
sh install.sh
mcp-customer-router service install --open

The installer checks the release archive's SHA-256, installs it in ~/.local/share/mcp-customer-router/, and adds mcp-customer-router to ~/.local/bin. It prefers /usr/bin/node or /usr/local/bin/node and otherwise records the node found on PATH. If that Node path later changes, run the installer again. It needs no root access and contains no customer records or credentials.

service install creates a systemd user service, mcp-customer-router.service, that starts when you log in. The dashboard opens at http://127.0.0.1:4773. Each person signs in to their own Glide organizations.

Open it each day with:

mcp-customer-router open

You can close the browser and terminal. The computer must stay awake for local agent work to continue. To keep the dashboard running while you are logged out, run loginctl enable-linger "$USER". Logs are in journalctl --user -u mcp-customer-router.

Related MCP server: aimcp

Set up a customer

1. Select New. Enter a name, business label, and the organization ID from the customer's Glide URL, after /o/. Keep v2 selected, or choose v1 for the full Glide tool set.

2. Select Connect Glide, complete sign-in, and choose that organization. If the browser does not open, select Open Glide sign-in. Wait for Organization verified.

3. Select Choose folder, or type the folder path, then select Preview config. Existing Glide connections start with Ignore selected. Choose Remove for any entries you want to remove, then apply the configuration.

4. Open that folder in your AI client and start a fresh session. Accept any project trust or MCP approval prompts. Ask the agent to list projects through customer-glide and check the organization before making changes.

The walkthrough opens on the first visit. The ⓘ button opens it again. Client setup provides instructions for each supported local client.

Choose folder uses zenity or kdialog when one is installed and the dashboard runs in your desktop session. Otherwise, type the absolute folder path.

Choose a client

Claude's desktop app, the Codex app, and Conductor are not available on Linux. Each AI provider still needs its own account. See client setup and verification limits.

Choose v1 or v2

Each customer uses one Glide MCP version at a time:

Customers saved before v2 support keep v1. To change a customer, open it and select Switch to v2 or Switch to v1 beside MCP endpoint. Switching ends the customer's open agent sessions. Linked folders use the new version from their next session; you do not need to apply their settings again.

Each version keeps its own Glide sign-in. The first switch to a version starts a sign-in. Switching back to a version used before only checks its saved sign-in. If v2 reports that your account lacks MCP v2 access, switch the customer to v1 or ask for access.

Add Glide Classic

A customer can also have a Glide Classic connection, for apps built in Glide Classic. It uses Glide's hosted Classic MCP (https://classic-mcp.prod.internal.glideapps.com/mcp), which needs a Glide employee account and is read-only.

1. Open the customer and select Set up Classic. Enter the Classic team ID if you know it, or leave it blank.

2. On the sign-in page, choose the customer's Classic team. If you left the team ID blank, check the team the router shows and select Use this team. Wait for Classic team verified.

3. Select Preview config for the customer's folder and apply it. The folder gets a customer-glide-classic entry beside customer-glide.

Classic keeps its own sign-in, separate from GlideOS. Reconnect Classic starts a new Classic sign-in and leaves GlideOS sessions open. For a customer with no GlideOS organization, leave the organization ID blank and select Also connect Glide Classic when you add it.

From the command line, mcp-customer-router classic --customer ID [--team ID] adds Classic, and connect, check and serve take --service classic.

Review existing connections

Preview config detects other Glide entries in supported project and user settings. Each new preview selects Ignore for every entry, which keeps it unchanged. Choose Remove explicitly to remove an entry when you select Apply and remove N. The review shows when removal affects other projects.

Changed files receive private backups, listed under Settings backups after Apply. To undo a removal, copy the required entry from its backup into the current settings file. Sign-in caches remain. If a settings file changes after preview, preview again before applying.

How it works

The router saves a separate Glide authorization for each customer. Linking a folder adds a customer-glide entry to .mcp.json and .codex/config.toml. Each client starts its own bridge process, which uses the customer's shared credential store and checks the saved folder binding and organization identity.

By default, customer records, bindings, credentials, and logs live in ~/.mcp-customer-router/. Settings backups stay beside the original files. The dashboard listens only on 127.0.0.1; each client bridge can continue with the dashboard closed.

Check identity reuses the saved authorization. Reconnect Glide starts a fresh authorization for that customer's current MCP version and invalidates its older router sessions. The other version's saved sign-in is kept. Open fresh client sessions after reconnecting. A separate folder or Git worktree needs its own binding.

Update or remove

Download and run the newer install.sh, then restart the service:

curl -fsSLO https://github.com/evanfurniss-dev/mcp-customer-router-linux/releases/latest/download/install.sh
sh install.sh
mcp-customer-router service restart

Stop active sign-in or identity checks before restarting, then open fresh agent sessions. The installer keeps one installed version and switches the stable ~/.local/share/mcp-customer-router/current link, so linked folders need no changes after an upgrade.

Moving from a source checkout

If you ran the router from a source checkout with your own systemd unit or ~/.local/bin/mcp-customer-router script, the installer and service install refuse to replace them. Stop and move them aside first:

systemctl --user disable --now mcp-customer-router.service
mv ~/.config/systemd/user/mcp-customer-router.service ~/mcp-customer-router.service.old
mv ~/.local/bin/mcp-customer-router ~/mcp-customer-router.old
systemctl --user daemon-reload

Then install as above. Customer data in ~/.mcp-customer-router/ is reused. If your old unit used another --home or --port, pass the same options to service install. Preview and apply each linked folder once to update its executable paths. The router refuses a change to a different customer or folder.

To remove the application while keeping saved customer data:

mcp-customer-router service uninstall
rm -rf ~/.local/share/mcp-customer-router
rm -f ~/.local/bin/mcp-customer-router

Scope and limits

• The connector supports Glide's v1 (https://mcp.glideapps.dev/mcp) and v2 (https://mcp.glideapps.dev/mcp/v2) MCP endpoints, and the hosted Glide Classic MCP.

• Connections are separated within one Linux account. An agent with broad file access can read other credential directories. This is not a sandbox for untrusted tenants.

• Execution stays on this computer. Cloud hosting and scheduled agent runs are outside this release.

• Credentials use private files. Removing a saved customer retains those files and does not revoke access at Glide.

• Other client connections and provider overrides can still expose tools. Check the active MCP list in each client.

• A timed-out or cancelled remote write may have completed. Read back its result before retrying.

See verification evidence for tested paths and remaining checks. Distributions other than Arch Linux and a fresh user's complete sign-in flow still need separate validation.

Development and support

Use mcp-customer-router --help for commands, or mcp-customer-router service status to inspect the local service.

Contributing and source setup · Report a bug · Security policy · Changelog · Release process

Attribution

Built on mcp-remote, based on commit 71cadf3aaa935608d5e14d472a59e9583ebb9505. The upstream bridge, copyright, and MIT license are retained. See the upstream README and UI source and license record.

This is an independent project. Glide and the named AI clients are trademarks of their respective owners; their names describe compatibility and do not imply endorsement.