Connect Claude
Administer your Foundry catalog from Claude — products, variants, inventory, and bills of materials — through the Foundry MCP connector.
Foundry ships an MCP connector so you can manage your catalog directly from Claude: search products, edit variants and pricing, adjust inventory, and build or inspect assemblies, all in conversation. The connector wraps the Foundry API, so everything it does respects the same permissions and organization scoping as any other API client.
What you can do
The connector exposes tools across the catalog:
- Products & variants — search, read, create, update, delete; edit SKUs, identifiers, and pricing on variants.
- Assemblies & BOMs — inspect a bill of materials, check how many units you can build from on-hand components, find where a component is used, flatten sub-assemblies, and replace or set a BOM.
- Catalog structure — brands, categories (including reordering), bundle components, and custom fields.
- Variant images — attach, reorder, and remove images by URL.
Every tool is a thin wrapper over an existing API endpoint and is gated by the connecting key’s permissions — if a key lacks a permission, the matching tool returns a permission error rather than acting.
Adding the connector
The connector lives at https://mcp.foundryims.com/mcp and supports two ways to authenticate.
Sign in with your Foundry account (recommended)
Add it as a custom connector in Claude and sign in through Foundry. This uses OAuth, so you never paste a key, and it supports multiple organizations — if your Foundry account belongs to more than one org, you switch between them from within Claude. Sessions refresh automatically.
- In Claude, add a custom connector pointing at
https://mcp.foundryims.com/mcp. - Complete the Foundry sign-in when prompted. Allow the sign-in popup — a popup blocker silently interrupting the login is the most common reason a connection appears to “complete” but doesn’t attach.
- Once connected, use the org-switching tools to pick which organization you’re working in.
Use an API key
Alternatively, authenticate with a Foundry admin API key (fims_…). This binds the connector to the single organization that owns the key — simpler when you only work in one org. Create a scoped key under Settings → API Keys (see Authentication & API keys) granting only the permissions you want the connector to have.
Scoping and safety
- The connector can only reach organizations your account (or API key) belongs to.
- Destructive tools (deleting a product, replacing a BOM) are marked as such; Claude will confirm significant changes with you before acting.
- Because access flows through your key’s permissions, a read-only key yields a read-only connector.
Related
- Authentication & API keys — create a scoped key for API-key mode.
- Core concepts — products, variants, and assemblies the connector operates on.