Resources · Claude connector

Claude Lens Studio connectorWhat Claude can do in your Lens Studio project.

The Claude Lens Studio connector exposes 3 tools. 0 only read, 2 change your open project, 1 is undocumented. Here: what Claude can add to a Lens, what has to be running on your machine first, and what the directory text promises without naming a tool.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when you build a Lens

Lens Studio is Snap's app for building Lenses, the augmented reality effects people use on Snapchat and on Spectacles glasses. This connector is a desktop extension: it runs on your computer and talks to the Lens Studio window you have open, so you can ask Claude for an asset or a package instead of hunting through menus.

Get a texture without leaving the conversation. Generate Texture sits behind the directory's promise of AI-generated textures, 3D models and face masks: you describe the look, and the result lands in your project.

Pull in a ready-made package. Install Lens Studio Package covers the directory's line about searching and installing packages, music and assets from libraries.

And one tool nobody explains. Set Lens Studio Property is listed with no description of its own, so this page does not tell you what it does.

Now the limits. Lens Studio must be open, version 5.15 or later, with an active session, or the extension cannot connect. It works in Claude Desktop only. Snap's text also promises building whole Lenses from a description, debugging and answering questions from a knowledge base, but none of the three listed tools is tied to those claims. Snap adds that its generative tools are tuned for Snapchat and may fall short on other platforms. Nothing runs on its own either: Claude acts while it answers you. The Integrations hub lists the other connectors.

Vocabulary

The vocabulary in one minute

Five words you will see while installing it.

Connector
The link you set up once between Claude and an app or account you use, so Claude can work in it while it answers you.
Tool
A named action the connector opens to Claude. Claude decides which to call; the directory lists the tools by their names.
Authorization
The permission prompt of the app itself, where you let Claude use it. Snap says you accept it once, on first use, then not again.
Approval
The confirmation Claude waits for before finishing an action that changes something, shown in the chat when it matters.
MCP
The common standard connectors are built on: it lets an assistant like Claude talk to an outside program such as Lens Studio.
Connect

Connect Lens Studio to Claude in three steps

  1. 01

    Find it in Claude Desktop

    In Claude Desktop, open Customize, then Connectors, and look for Lens Studio. On a Team or Enterprise workspace, an Owner or Primary Owner enables a connector for the organization before members can connect.

  2. 02

    Run the connection

    Claude's generic step is Connect on the connector's row. Lens Studio is a desktop extension, so the screens may differ from a remote connector: follow what Claude Desktop shows. Snap only says an authentication prompt appears on first use.

  3. 03

    Read what you grant

    Read the authentication prompt before you accept it. According to Snap, it does not come back in later sessions. Once the extension is connected, Claude's rule stays the same: it asks you before any action that changes something.

Tools

The 3 tools, sorted by what they do

Lens Studio gives Claude 3 tools: 0 that read your account, 2 that change something in it, and 1 no official source describes.

Two that change your project and one undocumented. Names stay exactly as Claude shows them.

  • 2 write
  • 1 not documented

What Claude changes (2)

2 tools

Two tools that add something to the Lens project you have open. No source describes a confirmation for either, so the general rule below applies.

Install Lens Studio Package

Approval: see the rule

Brings a package into your open project. Snap's directory text describes searching and installing packages, music and assets from Lens Studio's libraries.

What Claude asks for
no source describes a confirmation for this tool, so the default approval rule applies.
When it helps
you want a ready-made component for your filter instead of rebuilding it from scratch.

Sourceclaude.com · October 1, 2026 ↗

Generate Texture

Approval: see the rule

Produces a texture with Snap's generative AI and places it in your project, based on what you describe. The directory text groups it with generated 3D models and face masks.

What Claude asks for
no source describes a specific confirmation, so the general approval rule applies.
When it helps
a try-on Lens needs a worn denim look and you have no texture ready.
Watch out
Snap says its generative suite is tuned for Snapchat.

Sourceclaude.com · October 1, 2026 ↗

Undocumented (1)

1 tool

The directory publishes this name and nothing else. No official text says what it does, and this page will not guess from the name.

Set Lens Studio Property

This name appears in the directory's tool list and nowhere else with a description. Neither Snap's page nor any Claude page explains it, so this page says nothing more about what it does.

The general approval rule below applies to it as well.

Approvals

What Claude asks before it acts

By default, Claude stops and asks before any action it takes for you in an account or app. Here that covers the two tools that change your project, and the undocumented one too.

On a Team or Enterprise workspace, owners decide whether members can let some actions through without being asked each time. They can also bound what a connector may do for the whole organization, for example keeping reads and closing writes, and nobody overrides that from their own account. Claude works with the access of the person who connected it, nothing more. The official read-only versus write labels per tool sit only inside a connected account's settings, never on a public page.

Plans

Which plans it is on

Of the 819 sheets in the official directory, none shows availability per plan. Connector by connector, that answer is published nowhere.

The general rule is published: desktop extensions install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect. For the current state of Lens Studio, check its sheet in the official directory from your account.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: nothing happens when you save a project, publish a Lens or close the app.

The tool list is an observed floor, not a ceiling: an administrator could open more than any public page shows. The partner badge in the directory is not a security audit, and Anthropic writes on every sheet that it neither picks the tools a publisher exposes nor guarantees they behave as announced. Only Snap documents this connector, through its directory text; Claude's help center has no page on it, and Snap's linked overview names none of the three tools.

Need help

Need help connecting Lens Studio to Claude?

A person reads every message.

FAQ

Claude Lens Studio connector: common questions

01What can Claude do with the Lens Studio connector?
Claude can add things to the Lens project you have open in Lens Studio. Of its three listed tools, one generates a texture with Snap's generative AI, one installs a package from Lens Studio's libraries, and the third has no public description. Snap's directory text also mentions building Lenses from a description, debugging and a knowledge base, but none of those claims is tied to a listed tool. The extension works in Claude Desktop only.
02Can Claude change my Lens Studio project?
Yes, two of the three tools add something to it: a generated texture or an installed package. The third tool is listed without any description, so nobody can say from the sources whether it reads or changes anything. Snap's text also mentions manipulating scene objects, components and assets in conversation, without tying that to any of the three tools. As with every connector, an administrator could still open more than what any public sheet shows today.
03Does Claude ask before it changes my project?
By default, Claude asks for confirmation before any action it takes for you, and that is the rule covering the texture and package tools. No source describes a confirmation specific to either of them. Separately, Snap says you accept an authentication prompt the first time you use the extension and not again afterwards. On a Team or Enterprise workspace, owners decide whether members can let some actions through without being asked.
04Which Claude plans can use Lens Studio?
No official source publishes plan availability connector by connector, and none of the directory's sheets shows it. The general rule is that desktop extensions install on Claude Desktop, while remote connectors are open to all users across Claude's apps, with an Owner or Primary Owner enabling them first on Team and Enterprise. To see the current state of Lens Studio for your account, open its sheet in the official directory.
05Does Claude see everything on my computer?
No. The extension talks to the Lens Studio session you have open, and Claude works with the access of the person who connected it, nothing more. Its listed tools act on your Lens project; none of them is described as browsing your files in general. On Team and Enterprise Claude workspaces, an owner can also restrict or switch off the connector for everyone, and a member cannot override that from a personal account.
06Why does the Lens Studio extension not connect?
First check that Lens Studio is running. Snap's text says to launch Lens Studio 5.15 or later before installing the extension, and that an active session is required for it to connect. Check the version, open a project, then try again from Claude Desktop. Remember too that it is a desktop extension: the sheet lists Claude Desktop as its only surface, so the web app will not show it working.
07Claude or an automation tool for Lens Studio?
They do different jobs, so choose by task. Claude works in a conversation: you ask for a texture or a package, it adds it to your open project, then stops. It does not react on its own when you save or publish. If you need a repeatable pipeline that runs without you, an automation tool is the better fit. For a one-off request while you build a Lens, the conversation is enough.