Claude Brightdeck connectorWhat Claude can do in your Brightdeck account.
The Claude Brightdeck connector exposes 15 tools. 7 read your decks, 6 create, share or change them, and 2 have no documented effect. Below: what Claude can build, who it can invite, what it asks first, and where the export links stop.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when the deck comes out of the conversation
Brightdeck generates presentations that export to real PowerPoint files. With the connector, you describe the deck you need to Claude, it asks Brightdeck to build it, then shares or exports the result on request. The slides stay editable afterwards, in PowerPoint, Keynote or Google Slides, rather than arriving as flat images.
A first deck from a paragraph. deck_create_presentation turns a prompt into a themed presentation and sends back a live preview while the rest builds; deck_get_task_status tells Claude when it is done.
A deck built on your own documents. deck_create_presentation_v2 takes up to five reference files, such as a report or an old deck, so the slides draw on real material.
Sharing and handing over. deck_share_presentation invites a colleague with the right role, deck_list_permissions shows who already has access, and deck_export_pptx_url gives a download link for the final file.
What Claude will not do here. The export links last 60 minutes only. An invitation reaches the person you name even without a Brightdeck account. Two tools of the interactive flow have no documented effect. Nothing runs on its own either: no tool fires when a deck finishes building while you are away. Scheduled deck production belongs to an automation tool, a different job, gathered on the Integrations hub. For a project tool, see the Claude asana connector.
Five words before you plug it in
The vocabulary you will meet while connecting Brightdeck.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use later. Given once per person, and taken back the same way.
- Approval
- The confirmation Claude waits for before it goes through with a change to your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Brightdeck.
Connecting Brightdeck to Claude in three steps
- 01
Find Brightdeck in Claude
In Claude's settings, open Customize, then Connectors, and look for Brightdeck in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Brightdeck in the window the service opens itself. If the link breaks later, Disconnect and connect again from the same row.
- 03
Read the authorization screen
Read Brightdeck's screen before you accept it. It belongs to the service, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Brightdeck account itself.
The 15 tools, sorted by what they do
Brightdeck gives Claude 15 tools: 7 that read your account, 6 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it creates, shares or changes, and two tools without a documented effect. Tool names stay as Claude shows them.
- 7 read
- 6 write
- 2 not documented
What Claude reads (7)
7 toolsSeven tools that look at your decks, their status, access and export links without touching them.
deck_export_pdf_url
Hands back a signed link to download a deck as a PDF, the counterpart of the PowerPoint export for readers who only need to view it.
deck_export_pptx_url
Gives a signed link to download the deck as a real .pptx file, with shapes and text that stay editable in PowerPoint, Keynote or Google Slides.
deck_get_presentation
Looks up one deck and reports its details: file name, number of slides, visibility and your role on it. Claude uses it to check what it is about to work on.
deck_get_share_link
Returns the canonical view address of a deck along with its current visibility, which is what you paste into an email or a chat.
deck_get_task_status
Reports on a generation running in the background: its status, the stage reached and how many slides are done out of those planned.
deck_list_permissions
Shows who has access to a deck and with which role, from owner down to viewer. It is how Claude answers who holds which rights on a presentation.
deck_list_presentations
Lists the decks you own or can reach, newest first. Claude starts here when you refer to a deck by a vague name or by when you made it.
What Claude creates or changes (6)
6 toolsSix tools that build decks, invite or remove people, or change settings. No source describes their confirmation: the general rule below applies.
deck_create_blank_presentation
Approval: see the ruleStarts an empty deck to build slide by slide, instead of generating everything at once.
deck_create_presentation
Approval: see the ruleGenerates a complete, themed deck from a prompt. A live preview link comes back straight away while the rest of the slides keep building in the background.
deck_create_presentation_v2
Approval: see the ruleWorks like the prompt-based generator, but seeded with up to five reference files you upload: PDF, PPTX, DOCX or images. The deck draws on that material rather than on the prompt alone.
deck_revoke_permission
Approval: see the ruleTakes someone's access away from a deck. Claude can use it after checking the permission list, to tidy up who still sees a presentation.
deck_share_presentation
Approval: see the ruleInvites a person by email to a deck with a role: owner, admin, editor, commenter or viewer. If they have no Brightdeck account yet, they receive an invitation.
deck_update_presentation
Approval: see the ruleRenames a deck, switches its visibility between private, public view, public comment and public edit, or turns page numbers on and off.
Not documented (2)
2 toolsBrightdeck describes these two only as the engine of the interactive creation flow. No source says what each one does on its own, and this page will not guess.
deck_answer_questions
No official source says whether this tool reads or changes anything. Brightdeck only says, for this pair, that they drive the interactive creation flow in chat clients: clarifying questions first, then plan approval.
deck_approve_plan
Its exact effect is undocumented. The only sentence from Brightdeck covers it together with deck_answer_questions, as part of the interactive creation flow, and says nothing more precise about this one.
What Claude checks with you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the chat, right when it matters.
On Team and Enterprise, the owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping reading open and closing writing, for instance. That setting applies to everyone and nobody works around it from their own account. Claude also works with your Brightdeck account and nothing more: decks you cannot reach there stay out of its reach too.
Which Claude plans include it
Out of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state of this one, check the connector's sheet in the official directory. On Brightdeck's side, every integration needs a brightdeck.ai account, a condition set by Brightdeck.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a deck finishes building, a colleague comments or a link expires.
Everything here comes from Brightdeck's own documentation, the README of its public integrations repository: neither Claude's help centre nor Anthropic's developer docs have a page on this connector. The tool list is an observed floor, not a promise, since an admin can open actions no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic writes on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. Brightdeck also describes two tools only as a pair, which is why they stay in the undocumented group.
Need help connecting Brightdeck to Claude?
A person reads every message.
