Requirements

What you need before connecting an AI client to Hoursmith — Node 18+, an hsk_ API token, and a Studio or Agency workspace.

Three things stand between you and a connected assistant: a recent Node.js, a Hoursmith API token, and a workspace on a Studio or Agency plan. None take long.

Before you start

Plan: StudioAgency
Role: OwnerAdminManagerMember

API access is a Studio+ entitlement. Any role can mint a token, but the token only reaches what that role can — see Permissions & plans.

1. Node.js 18 or newer

MCP clients launch the server with npx, which ships with Node. You need Node.js 18+. Check your version:

node --version

If it prints anything below v18, update Node before continuing.

2. A Hoursmith API token

The server authenticates with a Hoursmith API token. Tokens start with hsk_ and are created in Settings → API.

Create a token

Create a new token and copy it immediately — it's shown only once. If you lose it, mint a replacement.

Keep it safe

You'll paste this token into your MCP client's config in the next steps. Treat it like a password.

For the full token workflow, see API tokens.

A token inherits the role of the member who created it. An Owner or Admin token reaches the whole workspace; a Member token is limited to their own time and the projects they're on. Mint the token from a membership with the access you want your assistant to have.

3. A Studio or Agency plan

API access — and therefore MCP — is included on the Studio Studio and Agency Agency plans. On the Free plan, every MCP call fails with a 402 plan error.

If you're on Free, upgrade in Billing & plans, then create your token.

That's it

No separate install is needed — your MCP client launches the server on demand with npx. Next, see Install for how that works, then configure your client.

Was this page helpful?