Skip to main content
Claude Desktop and Claude Code connect to plamotrack using your instance’s MCP endpoint and a personal access token. Once connected, Claude can log orders, check your collection, adjust stock, and more — just by talking.

Prerequisites

You need a personal access token before you configure the client. Create one at Settings → Access tokens in plamotrack. Read-only is enough for an agent that just looks things up; read-and-write lets it log orders, move kits along the pipeline, and adjust stock. See Access Tokens for more detail.

Claude Desktop

1

Open the Claude Desktop config file

The config file location depends on your operating system:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
2

Add the plamotrack entry

Claude Desktop requires a stdio connection, so use mcp-remote to bridge plamotrack’s HTTP endpoint. Add the following to your config, replacing ptk_your_token_here with your actual token:
claude_desktop_config.json
Replace http://localhost:8080/mcp/ with your instance URL if it’s different.
3

Allow plain HTTP if needed

If your instance URL is plain http:// and Claude Desktop complains, add "--allow-http" to the end of the args array. An https:// instance doesn’t need this flag.
4

Restart Claude Desktop

Save the config file and restart Claude Desktop for the change to take effect.
5

Verify the connection

The plamotrack tool should now appear in Claude Desktop. Try asking: “What’s in my Gunpla backlog?”
The token goes in the env block rather than directly in args because Claude Desktop splits args on spaces on some platforms, and Bearer ptk_… contains a space. Putting it in env and referencing it as ${PLAMOTRACK_AUTH} sidesteps the issue entirely.

Claude Code

Run this command, replacing the URL and token as needed:
Claude Code talks to the endpoint directly, no bridge needed, and picks the current MCP protocol revision on its own. There is nothing else to configure.

Verifying the connection

Once connected, try asking Claude one of these to confirm everything is working:
  • “What’s on my build bench?”
  • “How many kits do I have in backlog?”
Claude should call plamotrack’s tools and answer based on your actual collection.
If your instance isn’t on localhost — for example, it’s on a LAN hostname like nas.lan — make sure that hostname is listed in ALLOWED_HOSTS in your .env file. Without it, plamotrack returns 421 Misdirected Request and the connection fails. See Local & LAN for details.
A client configured without a token is refused at its very first request, whichever protocol revision it speaks. If Claude reports that the server needs authentication, check that the Authorization header or the env value carries Bearer ptk_… with the space in between.