MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external services. plamotrack implements it natively — no plugin, no middleware, no separate process.
What you can do
Your AI assistant has access to over 30 tools covering your entire collection. Here are a few examples of what that looks like in practice:- “The Sinanju arrived” → Claude calls
mark_order_received, the kit moves to backlog, and your Gundam Markers are on hand. - “Add that Gundam Express order from my email” → Claude reads the email, calls
create_order, and kits and supplies are logged against a new pending order. - “What’s on my bench?” → Claude calls
list_kitsfiltered to Building status and tells you exactly what you’re supposed to be working on.
Two ways to connect
Personal access token
Create a token in Settings → Access tokens, then paste it into your AI client’s config. Works with Claude Desktop, Claude Code, and any client that can send an HTTP header. Best for local and LAN instances.
OAuth sign-in
For Claude.ai and ChatGPT on the web. Requires OIDC mode and TLS. You sign in through your identity provider — no token to paste or store.
The MCP endpoint
The MCP endpoint is at<your instance>/mcp/. Always include the trailing slash.
Agent skills
The MCP tools are deliberately generic — nothing in plamotrack knows what an “HG” grade is or how Bandai kit numbers work. You can teach your AI assistant those conventions by installing an agent skill: a small instruction file that loads alongside your MCP connection and keeps records consistent. Theplamotrack-gunpla skill covers kit naming, grade buckets, series naming, Gundam Markers, and more. See the Agent Skills page for how to install one.