Manage your catalog from Claude

In scope today

• • Products and variants — search, create, edit, trash, restore
• • Assemblies and bills of materials, including buildability and reverse lookups
• • Bundle components
• • Brands and categories
• • Variant images, by URL
• • Custom field definitions and values

Not in scope

• • Orders, invoices, and purchase orders
• • Stock adjustments and physical counts
• • Channel listings and pushes to your storefronts
• • Users, roles, and billing

Stock adjustments and purchase orders are the next surfaces planned. If you want one of these sooner, tell us — demand decides the order.

claude.ai and Claude Desktop — log in

Open Settings → Connectors, find Foundry IMS in the directory, and click Connect. You'll sign in with your normal Foundry account and approve the connection. No keys to copy.

Your session covers every organization your account belongs to. Say "switch to DieselPowerSource" and Claude moves — or just name the org in your request. Sessions renew on their own for about a day at a time.

Claude Code — use an API key

Create a key in Foundry under Settings → API Keys → Create API Key, then add the server:

claude mcp add --transport http foundry https://mcp.foundryims.com/mcp \
  --header "Authorization: Bearer fims_your_key_here"

An API key is bound to exactly one organization. To work across several, add the connector once per org under distinct names — foundry-rigcables, foundry-dps — and Claude will route by the name you say.

Claude API — build it into your own app

Claude can reach the connector directly from the Messages API. Declare the server and grant access to its tools — both halves are required:

client.beta.messages.create(
    model="claude-opus-5",
    max_tokens=4096,
    betas=["mcp-client-2025-11-20"],
    mcp_servers=[{
        "type": "url",
        "url": "https://mcp.foundryims.com/mcp",
        "name": "foundry-ims",
        "authorization_token": "fims_your_key_here",
    }],
    tools=[{"type": "mcp_toolset", "mcp_server_name": "foundry-ims"}],
    messages=[{"role": "user", "content": "Which variants are missing a UPC?"}],
)

The mcp_server_name must match the server's name. Declaring the server without the matching mcp_toolset entry is rejected as a validation error.

Grant only what the job needs

For catalog work, the Catalog Editor preset is the clean choice — or tick exactly products.read/write and variants.read/write. A products-only key physically cannot reach orders, invoices, or users, even if a model tries. Want Claude to look but never edit? Issue a read-only key.

Deletes are recoverable

delete_product moves a product to the trash rather than destroying it, and restore_product brings it back. Claude is instructed to confirm with you before deleting a product or replacing a BOM, since both are significant changes.

Storefront keys are rejected

Public storefront keys (fims_sf_*) can't be used here. This is an admin surface and expects an admin key.

Find things

Search matches identifiers, not just names — paste a SKU, UPC, GTIN, MPN, or a channel/supplier SKU straight in.

Products & variants

A product holds one or more variants; the variant is the sellable SKU that carries price, cost, and identifiers.

Assemblies & bills of materials

Inspect a recipe, ask what you could build from stock on hand, or swap a component everywhere it appears.

Bundles

Kits assembled at the point of sale rather than on the shop floor.

Brands & categories

Resolve or create the brand and category records a product needs.

Images

Add images by URL — Foundry re-hosts them, so a vendor link going dead later does not empty your listing.

Custom fields

Read the field definitions, then read or write values on a product or variant.

Organizations

Only relevant if your login covers more than one Foundry organization.