COUNTCOUNT
Sign Up

Tutorials

Set up the COUNT CLI

Install the CLI, hand it your partner credentials, log in through the browser once, and it will hold the tokens and sign requests for you — including as a local MCP server for an agent.

4 steps · about 33 seconds · from npm install to an agent wired up

What you just saw

  1. 1count init stores credentials locallyThe clientId and clientSecret go into ~/.count/credentials.json on your own machine. The CLI signs requests locally, so the secret is never transmitted.
  2. 2count login needs its callback registeredThe CLI listens on a fixed loopback URI and COUNT redirects back to it. That exact URI has to be in your app’s redirect URLs, or the login fails on a redirect mismatch that looks like a CLI bug.
  3. 3Consent is the same screen a partner app usesYou authorize the CLI per workspace, exactly as an end user would authorize your product, and the token is stored against that workspace.
  4. 4count mcp serves the same tools over stdioprint-config emits the JSON your MCP client wants. The agent then talks to COUNT through a process you control, with the token staying on your disk.

Where to go next

COUNT CLI referenceMCP ServerAPI access credentials