← LoadsterCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Loadster
Snapshot Sep 30, 2026 · 23:10 UTC · version 1.2.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "setup",
"description": "Connect Claude Code to Loadster's MCP server and verify the connection. Use when Loadster tools are missing, a Loadster tool returns 401 or unauthorized, or the user asks to set up, connect, or reconnect Loadster.",
"included_files": [],
"skill_md_contents": "---\nname: setup\ndescription: Connect Claude Code to Loadster's MCP server and verify the connection. Use when Loadster tools are missing, a Loadster tool returns 401 or unauthorized, or the user asks to set up, connect, or reconnect Loadster.\n---\n\n# Setting up the Loadster MCP connection\n\nThe Loadster plugin registers one MCP server, `loadster`, at `https://api.loadster.com/mcp`. It authenticates with\nOAuth, so the user has to approve the connection once in their browser. You cannot complete that approval for them,\nbut you can get them there and confirm the result.\n\n## Check whether Loadster is connected\n\nCall `list_projects`. Three outcomes:\n\n- **It returns projects.** The connection works. Tell the user which team's projects came back, because access is\n scoped to the team they connected in.\n- **The tool is missing.** The plugin's MCP server hasn't started or isn't authenticated. Follow the steps below.\n- **It fails with 401 or \"unauthorized\".** The OAuth connection was revoked, or the user is using a token that was\n revoked or mistyped. Follow the steps below.\n\n## Connect with OAuth\n\nAsk the user to:\n\n1. Run `/mcp` in Claude Code.\n2. Select **loadster** from the list and choose **Authenticate**.\n3. Approve the connection in the browser window that opens. If they belong to more than one Loadster team, the\n team they pick there is the one the agent will work in.\n4. Come back and confirm.\n\nThen call `list_projects` again to verify.\n\n## Connect with an MCP token instead\n\nOnly for headless use, CI, or clients where OAuth isn't possible. Tell the user to create a token in the Loadster\ndashboard under **Settings → AI Agents → MCP Tokens**, copy it immediately (it's shown once), and register the server\noutside the plugin:\n\n```bash\nclaude mcp add --transport http loadster https://api.loadster.com/mcp --header \"Authorization: Bearer YOUR_TOKEN\"\n```\n\nNever ask the user to paste a token into the conversation, and never write a token into a file that will be\ncommitted.\n\n## Troubleshooting\n\n- **Stale or missing tools after a change:** ask the user to run `/mcp` and reconnect, or restart Claude Code.\n- **Wrong team's projects:** the user has to disconnect and reconnect, choosing the right team during OAuth.\n- **Still stuck:** point them at https://loadster.com/manual/ai-agents/ or help@loadster.com.\n"
}SHA-256: 245525b674c11f037f67e6695062a5996be7fefcfc3e43744aae58e4489b2c82