Sudomimus MCP server

The Sudomimus MCP server connects a local MCP host to your With account. It runs as a stdio child process and uses the Sudomimus CLI session. Sign-in still requires your approval in a browser.

The current tools are:

Tool	What it reads
whoami	The current account identity
list_organizations	Organizations available to the account
list_applications	Applications in one organization
get_application	One application by its public anchor

List tools accept an optional opaque cursor. Pass a returned cursor unchanged to read the next page. The MCP server uses the CLI credential store. With applies the same account and organization authorization checks as it does for the CLI.

Sign in and connect

Use Node.js 26 or newer. When the sudomimus-mcp package is available in your environment, install it and approve the device sign-in:

npm install --global sudomimus-mcp
sudomimus-mcp login

In your MCP host, add a local stdio server with command sudomimus-mcp and no arguments. The host starts the server process when it needs tools. Do not start the server command in a terminal that expects a human-readable prompt.

To use a source checkout instead, install the repository dependencies, build clients/mcp, and configure the host to run node with the absolute path to clients/mcp/dist/index.js as its argument. Run node clients/mcp/dist/index.js login from the repository root before starting the host.

Run sudomimus-mcp logout to revoke and clear the installed package’s local session. For a source checkout, use node clients/mcp/dist/index.js logout.

This MCP server uses a person’s approved CLI session. For an unattended service, create a separate agent or automation identity with its own credential.