Connect an AI assistant (MCP)¶
Gridstock has a built-in MCP server. MCP (the Model Context Protocol) lets an AI assistant — such as Claude — securely work with your inventory on your behalf. Once connected, you can ask it things like "how many 100nF 0402 caps do I have free, and where?" or "allocate four BC547s to the amp build", in plain language.
Connecting an assistant is included on every plan and is never charged for separately.
What you need¶
- A Gridstock account you can sign in to (see Getting started).
- An MCP-capable assistant — for example Claude Desktop, the Claude mobile/web app, Claude Code, or any client that supports remote MCP servers over HTTP.
The server address¶
This is a remote server — you connect to it by URL and sign in through your browser. There are no API keys to copy or paste.
Connect¶
The exact menu wording varies by client, but the shape is always the same:
- In your assistant, open its connectors / MCP servers settings and choose to add a remote (HTTP) MCP server.
- Paste the server address above.
- Save. The assistant opens a browser sign-in — this is Gridstock's normal Clerk sign-in. Sign in the same way you sign in to the website.
- Choose the organisation you want the assistant to work with when prompted. The connection is scoped to that organisation's data.
- You're connected. The assistant can now use the Gridstock tools below.
Pick the right organisation
The assistant only ever sees the one organisation you chose at sign-in. To work with a different organisation, reconnect and pick that one.
Claude Desktop / Claude apps¶
Add it under Settings → Connectors → Add custom connector, paste the URL, and complete the browser sign-in.
Claude Code¶
Add a remote MCP server pointing at the URL, for example:
Then run /mcp inside Claude Code and follow the prompt to authenticate in your
browser and select your organisation.
What the assistant can do¶
Once connected, the assistant has tools to:
- Search & read — search components, get a component's details, list locations, list projects, list devices, see a device's or project's allocated components.
- Manage components — create, update and delete components (names, quantities, type, storage location).
- Manage storage — create, update and delete locations.
- Manage projects & devices — create and update projects and devices.
- Allocate — allocate and deallocate components to devices, and find scavenge candidates when stock runs out.
You stay in control: the assistant proposes actions and your client asks you to approve anything that changes your data.
Example things to ask¶
- "What components am I low on?"
- "Add 25 of '1N4148 SOD-123' in Rack 03 / Diodes."
- "Which projects could I scavenge an ATmega328 from?"
- "Allocate two SSD1306 OLED modules to the clock build."
- "Where do I keep my 0.1µF decoupling caps?"
Troubleshooting¶
The assistant says it's unauthorised, or tools return a 401.
Your session needs refreshing, or no organisation was selected. Re-run your client's
authentication for the Gridstock connector (in Claude Code, run /mcp), sign in
again, and make sure you pick an organisation.
I connected but see no data / the wrong data. You're almost certainly connected to a different organisation than you expected. Reconnect and choose the right one at sign-in.
Make sure you used the MCP address, https://mcp.gridstock.wallace.network/mcp
— not the website address gridstock.wallace.network, which serves the app, not
the MCP server.