Configure Claude Desktop

Add the Hoursmith MCP server to Claude Desktop — config file paths for macOS and Windows, the JSON block, and the required restart.

Claude Desktop reads its MCP servers from a single JSON file. Add the Hoursmith block, drop in your token, and restart.

Before you start

Plan: StudioAgency

You need Node.js 18+ and an hsk_ API token. Have the token ready before you start.

Add the server

Open the config file

The file lives in a different place on each platform.

~/Library/Application Support/Claude/claude_desktop_config.json

%APPDATA%\Claude\claude_desktop_config.json

If the file doesn't exist yet, create it.

Add the Hoursmith block

Paste this into the file, replacing hsk_live_... with your own token:

{
  "mcpServers": {
    "hoursmith": {
      "command": "npx",
      "args": ["-y", "@hoursmith/mcp-server"],
      "env": { "HOURSMITH_API_TOKEN": "hsk_live_..." }
    }
  }
}

If you already have other servers under mcpServers, add hoursmith alongside them rather than replacing the whole object.

Restart Claude Desktop

Fully quit and reopen Claude Desktop. Config changes only take effect after a restart.

A reload isn't enough — you must fully quit Claude Desktop (not just close the window) and open it again for the new server to appear.

Verify it worked

Once Claude Desktop restarts, the Hoursmith tools become available. Try a read-only prompt to confirm the connection:

Show me my Hoursmith profile.

That runs the get_me tool. If it returns your account details, you're connected. For things to try next, see Example prompts.

Your token never leaves your machine — it lives only in this config file and is passed to the server as an environment variable. See Security.

If it doesn't connect

Most failures come down to the token, the Node version, or the config path. Walk through Troubleshooting or MCP won't connect.

Was this page helpful?