We want to make it easier for admins to stay current on what's changing in Benchling. Here’s some updates you might have missed this summer.
Benchling is available through MCP [Benchling AI]
Ask Claude, ChatGPT, or any other MCP-capable assistant about Benchling data without switching windows. Benchling now exposes its AI agents through the Model Context Protocol (MCP), routing the query through Benchling's audited agents and returning the answer inline. Tenant admins enable the connector in the Tenant Admin Console, and Benchling is listed in the Claude Connectors directory.
Protein tag, cleavage site, and more flexible linker support [Biologics]
Antibody chains can now include extra residues, such as purification tags, cleavage sites, or linkers, at the N- and C-termini and between certain domains. Every protein format now includes optional "element" domains that hold any residues, giving customers a place to model these additions without reshaping the chain. “Elements” can represent a linker, a cleavage site, or a tag, alone or combined.
Improved visibility into AI credit usage [Benchling AI]
Where the AI usage chart previously showed only a running total, tenant admins can now filter it by product and by user to see exactly where credits are going. A new CSV export adds the same detail on demand, listing the user, feature, and credit amount for every usage event, all without leaving the Tenant Admin Console.
Mixture Prep tables support formulas and table mapping [Notebook]
No more manually copying values in and out of Mixture Prep tables. Mixture Prep tables can now hold formulas and serve as sources or destinations for Table Mapping, so mixture data flows through the Notebook like any other structured table. For even more flexibility, Metadata fields can be resized, reordered, and deleted, and Lookup and Custom columns can now be added to Ingredients.
Advanced validation rules for entity schemas [Registry]
What happens when a single validation rule needs to check more than one field at once? Advanced Validation Rules make that possible on entity schemas: compare multiple fields in a rule, reference linked entities up to five levels deep, apply conditional logic, and run date-based calculations.
Limit access to workflow task schemas [Workflows]
Workflows admins can now set task schema access to READ or NONE, making it possible to hide deprecated workflows and reduce clutter when users create tasks.
Questions? Reach out to Support.