Claude Fibery connectorWhat Claude can do in your Fibery account.
The Claude Fibery connector exposes 88 tools. 29 read your workspace, from schema to activity history, and 59 write, from a comment to a whole new space, all documented by Fibery. Below: what Claude reads, what it can change or delete, and what nobody can undo.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Fibery connector changes for product teams
A product manager wants a sprint health report before Monday: what is at risk, what is overdue, what shipped. Normally that means opening three boards, filtering, copying numbers into a doc. With the connector she asks Claude. Claude runs the team's saved views, checks the activity log, flags items with no recent updates and writes the summary into a Fibery document.
Ask the workspace anything. schema and schema_detailed show Claude what spaces, databases and fields exist, then query filters, sorts and aggregates records, while search covers names, documents and comments. search_history answers who did what and when, which is how a stand-up recap or release notes get written without digging.
Act on records and documents. create_entities, update_entities and set_state handle the everyday: file a bug, mark it urgent, move features to Done. In documents, insert_document_blocks and replace_block_text write or fix content precisely, and add_inline_comments leaves review notes where they belong.
Reshape the workspace itself. Claude can open a space with create_space, add databases and fields of every type including formulas, build views with create_view, assemble reports, draw on whiteboards and set up automation rules with create_automation. Fibery describes it as Claude doing almost anything you can do yourself.
That power has an edge. delete_entities removes records permanently, and Fibery states it cannot be undone; spaces, databases, fields and automations can be deleted too. Nothing runs by itself from the conversation either: Claude acts when asked, and recurring jobs belong to Fibery automations or to the Fibery n8n integration and the Fibery Make integration.
Five words before you plug it in
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude chooses the ones it needs as it answers; the directory lists each by name.
- Authorization
- Fibery's own sign-in screen, reached after you type your workspace address, where you grant Claude its access. Given once per person.
- Approval
- The confirmation Claude waits for in the conversation before going ahead with something that would alter your workspace.
- MCP
- The common standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Fibery.
Plug Fibery into Claude in three steps
- 01
Find Fibery in Claude
In Claude's settings, open Customize, then Connectors, and look for Fibery. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; after that, each member signs in on their own.
- 02
Start the connection
Click Connect on the Fibery row. Fibery asks for your workspace address, then opens its own sign-in window. If the link breaks later, use Disconnect and connect again from the same list.
- 03
Read the authorization screen
Look at Fibery's authorization screen before you accept. It belongs to Fibery, not to Claude, and it decides what the access covers. You can take that access back later from Fibery as well.
The 88 tools, sorted by what they do
Fibery gives Claude 88 tools: 29 that read your account, 59 that change something in it.
Two groups: what Claude reads and what it writes. Fibery documents every tool on the sheet, so there is no undocumented group here. Names stay as Claude shows them.
- 29 read
- 59 write
Tools index
- display_automations_schema
- display_entity_capabilities_via_sharing
- display_report_schema
- display_schema_capabilities
- download_file
- fetch_by_url
- fetch_view_data
- get_app_accounts
- get_automation
- get_automations
- get_connectors_list
- get_custom_apps_list
- get_entity_links
- get_entity_mention
- get_fibery_skill
- get_files_meta
- get_manual_import_link
- get_me
- get_report
- get_reports_list
- get_user_mention
- query
- query_views
- read_document
- schema
- schema_detailed
- search
- search_guide
- search_history
- add_chart_tab
- add_collection_items
- add_comment
- add_file_from_url
- add_inline_comments
- add_metric_tab
- add_table_tab
- create_automation
- create_avatars_fields
- create_comments_fields
- create_custom_app
- create_custom_app_dev_token
- create_databases
- create_entities
- create_files_fields
- create_formula_field
- create_icon_fields
- create_multi_select_fields
- create_primitive_fields
- create_relation_fields
- create_report
- create_single_select_fields
- create_space
- create_view
- create_workflow_field
- delete_automation
- delete_avatars_fields
- delete_comments_fields
- delete_databases
- delete_document_blocks
- delete_entities
- delete_fields
- delete_icon_fields
- delete_space
- delete_views
- delete_workflow_field
- execute_whiteboard_commands
- insert_document_blocks
- move_document_blocks
- remove_collection_items
- remove_dimension
- remove_tab
- rename_databases
- rename_fields
- replace_block_text
- reply_document_comment
- set_block_attrs
- set_block_text
- set_state
- update_automation
- update_dimension
- update_entities
- update_formula_field
- update_multi_select_fields
- update_report
- update_single_select_fields
- update_tab
- update_view
- update_workflow_field
What Claude reads (29)
29 toolsTwenty-nine tools that explore the schema, query records, read documents, reports and automations, or check permissions.
display_automations_schema
Shows which actions and arguments are available for a given database and automation type, the menu Claude checks before it builds or adjusts a rule.
display_entity_capabilities_via_sharing
Reports per-record access that comes from sharing: direct shares, access templates and assignment rules based on People fields, so you see who reaches a record and why.
display_report_schema
Gives the report source schema for one or more databases, in other words what a report is able to draw from and which fields it can use.
display_schema_capabilities
Reports what the current user can and cannot do at the space and database level across the workspace, a map of your own permissions.
download_file
Fetches a file attachment and returns a signed download link, valid for about an hour, plus its metadata; small images and supported text files come back inline for Claude to inspect.
fetch_by_url
Takes a Fibery link to a record or a view and returns what sits behind it, rendered as readable text in the conversation.
fetch_view_data
Runs a saved view and returns the records it would display, with the view's own filters applied, so Claude sees exactly what the team sees.
get_app_accounts
Lists the external app accounts connected to the workspace, such as Slack or email, whose identifiers some automation actions require.
get_automation
Fetches one automation rule or button by its identifier, with its triggers, filters and actions spelled out, so Claude can explain what it really does.
get_automations
Lists the automation rules or buttons of one database, with their triggers, filters, actions and the identifiers needed for any later adjustment.
get_connectors_list
Lists the built-in import integrations Fibery offers, such as Trello, Notion, Jira or CSV, so Claude knows which migrations are native.
get_custom_apps_list
Shows the custom apps present in the workspace, the small React apps embedded in Fibery views, so nobody builds the same widget twice.
get_entity_links
Returns direct Fibery web links to records from their public identifiers, like #13961, ready to paste anywhere.
get_entity_mention
Builds a live reference to a record, ready to embed in document content through the document tools, so the mention keeps pointing at the right record.
get_fibery_skill
Loads the full reference guide for one Fibery domain: query, documents, views, reports, automations, whiteboard or custom apps.
get_files_meta
Lists the file attachments sitting on records, with their details, so Claude knows what is attached where without opening every record.
get_manual_import_link
Generates a link to Fibery's import wizard for a given connector and target database, so you finish the import yourself in the right screen.
get_me
Returns the name, email and identifier of the person signed in, the context Claude needs whenever a request is about your own work.
get_report
Fetches a report by its identifier, with its tabs, sources and configuration, so Claude understands how it is put together.
get_reports_list
Lists every report view in the workspace, with enough detail for Claude to pick the right one or notice that none exists yet.
get_user_mention
Builds a user mention ready to embed in document content through the document tools, so a person is tagged properly rather than just named.
query
Fetches records from any database with filtering, sorting, pagination and aggregation, including sub-queries such as each feature with its linked bugs. Fibery calls it the main read tool.
query_views
Lists saved views, boards, timelines, grids or documents, together with their configuration, so Claude can reuse the team's own lenses on the data.
read_document
Reads a document as a flat list of addressable blocks with stable identifiers, plus any inline comment threads attached to them.
schema
Lists every space and database in the workspace. Fibery says Claude calls it first before almost anything else, to know what exists and where.
schema_detailed
Zooms into one database and shows all its fields, their types and their possible values, such as every workflow state, which Claude needs to work accurately with that data.
search
Runs a full-text keyword search across the workspace, covering entity names, document content and comments, and returns a ranked list of matches.
search_guide
Searches Fibery's official documentation to answer questions about how Fibery itself works, rather than about the data in your workspace.
search_history
Looks up the activity log, who did what and when, with filters on database, record, author, date range and action type. By default it covers the last 24 hours, up to 50 events per call and at most 100.
What Claude writes (59)
59 toolsFifty-nine tools that add, change, move or delete records, documents, fields, views, reports and automations. No source describes a confirmation specific to them: the general rule below applies.
add_chart_tab
Approval: see the ruleAppends a chart tab to an existing Fibery report, so the numbers of a report also show up as a visual.
add_collection_items
Approval: see the rulePuts items into a collection field of an entity: assigning a person, attaching a tag or linking a related record.
add_comment
Approval: see the rulePosts a comment on an entity, or a reply to an existing comment on the same entity.
add_file_from_url
Approval: see the ruleDownloads a file from a web address and attaches it to an entity's file field.
add_inline_comments
Approval: see the ruleAnchors comments to selected text inside a document, the same threads people see in the Fibery editor, several at once if needed.
add_metric_tab
Approval: see the ruleAdds a metric tab to a report, a single headline number instead of a table or chart.
add_table_tab
Approval: see the ruleAdds a table tab to a report, for readers who prefer rows and columns to a chart.
create_automation
Approval: see the ruleSets up an automation rule or a button for a database; rules need at least one trigger, buttons run when someone clicks them.
create_avatars_fields
Approval: see the ruleSwitches on avatar images for the entities of a database.
create_comments_fields
Approval: see the ruleEnables comments on the entities of a database, so people can discuss each record.
create_custom_app
Approval: see the ruleScaffolds a new custom app, one of the small React apps embedded in Fibery views, from Fibery's starter template.
create_custom_app_dev_token
Approval: see the ruleIssues a short-lived access token for developing a custom app locally.
create_databases
Approval: see the ruleBuilds one or more databases inside a space, the containers that hold a kind of record such as bugs or features.
create_entities
Approval: see the ruleAdds one or more new records to a database: bugs, features, tasks, customer requests.
create_files_fields
Approval: see the ruleAdds a file attachment field to a database so records can carry documents.
create_formula_field
Approval: see the ruleCreates a calculated field from a plain-English description; Fibery generates the formula itself.
create_icon_fields
Approval: see the ruleTurns on emoji icons for the entities of a database, a small visual marker shown next to each record's name in lists and boards.
create_multi_select_fields
Approval: see the ruleAdds a multi-choice, tag-style field to a database.
create_primitive_fields
Approval: see the ruleAdds simple fields to a database: text, number, date, date range, checkbox, URL, email, phone, location or rich-text document.
create_relation_fields
Approval: see the ruleLinks two databases with a relation field, choosing its cardinality such as one-to-many or many-to-many, so records on both sides can point at each other.
create_report
Approval: see the ruleBuilds a new report with its data sources and a title.
create_single_select_fields
Approval: see the ruleAdds a single-choice dropdown with coloured options to a database.
create_space
Approval: see the ruleOpens a new top-level space in the workspace.
create_view
Approval: see the ruleProduces a new view: grid, list, board, timeline, calendar, gantt, gallery, map, feed, embed, form, standalone document or whiteboard.
create_workflow_field
Approval: see the ruleDefines the workflow field of a database: its stages and whether each one counts as not started, started or finished.
delete_automation
Approval: see the rulePermanently deletes an automation rule or button.
delete_avatars_fields
Approval: see the ruleTurns avatar images back off for a database's entities.
delete_comments_fields
Approval: see the ruleDisables comments on the entities of a database, removing the discussion thread that sat on each record.
delete_databases
Approval: see the ruleRemoves databases from a space.
delete_document_blocks
Approval: see the ruleDeletes blocks from a document, each with everything nested under it.
delete_entities
Approval: see the rulePermanently deletes records. Fibery states that it cannot be undone.
delete_fields
Approval: see the ruleRemoves one or several fields from a database, taking them out of every record of that database.
delete_icon_fields
Approval: see the ruleSwitches emoji icons off for a database, so its records show their names without the small marker.
delete_space
Approval: see the ruleRemoves a whole top-level space.
delete_views
Approval: see the ruleClears one or several views out of the workspace, while the records they displayed stay exactly where they were.
delete_workflow_field
Approval: see the ruleDeletes the workflow field of a database together with the stages it defined for each record.
execute_whiteboard_commands
Approval: see the ruleCreates, updates or deletes whiteboard elements: shapes, text, links, sticky notes, sections and freehand strokes.
insert_document_blocks
Approval: see the ruleInserts new blocks from Markdown, such as headings, paragraphs, lists, tables or images, before or after a block or at either end of the document.
move_document_blocks
Approval: see the ruleMoves blocks, with all their children, to a new position in the document.
remove_collection_items
Approval: see the ruleTakes items out of a collection field: unassigning a person, dropping a tag, unlinking a record.
remove_dimension
Approval: see the ruleRemoves a dimension within a report tab, for example the breakdown that splits a chart by team or by month.
remove_tab
Approval: see the ruleDeletes a tab from a report, whether it held a chart, a metric or a table.
rename_databases
Approval: see the ruleRenames databases, and can also move one to a different space.
rename_fields
Approval: see the ruleGives one or several fields of a database a new name, without touching the values they hold.
replace_block_text
Approval: see the ruleSwaps one exact text occurrence inside a block and leaves the rest untouched, so formatting and comments survive; Fibery calls it the preferred tool for small fixes.
reply_document_comment
Approval: see the ruleAdds replies to existing inline comment threads, several in one call if needed.
set_block_attrs
Approval: see the ruleChanges block attributes: heading level, task done or to-do state, code language, callout icon.
set_block_text
Approval: see the ruleRewrites the inline content of one or more existing text blocks from Markdown, keeping each block's type, attributes, identifier and position.
set_state
Approval: see the ruleMoves a record to another workflow state, for example from In Progress to Done, the way someone would drag a card across a board.
update_automation
Approval: see the ruleModifies an existing rule or button: rename it, enable or disable it, replace triggers or filters, and add, change or delete actions.
update_dimension
Approval: see the ruleAdjusts a dimension within a report tab, such as the field a chart is grouped by.
update_entities
Approval: see the ruleUpdates fields on existing records; only the fields you name are changed.
update_formula_field
Approval: see the ruleUpdates a calculated field, again from a plain-English description that Fibery turns into the formula.
update_multi_select_fields
Approval: see the ruleModifies a multi-choice field and its options, such as adding, renaming or recolouring a choice.
update_report
Approval: see the ruleUpdates a report's title and/or its data sources, leaving its tabs in place.
update_single_select_fields
Approval: see the ruleEdits a single-choice dropdown and its coloured options, for example a label or a colour.
update_tab
Approval: see the ruleAdjusts scalar properties of a report tab, such as its name or simple display settings.
update_view
Approval: see the ruleEdits an existing view's name, description, space or configuration.
update_workflow_field
Approval: see the ruleReshapes the workflow field of a database: its stages and whether each counts as not started, started or finished.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request appears in the conversation when it matters.
On a Team or Enterprise workspace, owners decide whether members may let some actions through without a prompt each time. They can also restrict what a connector may do across the organization, keeping queries open and closing every write, and nobody overrides that from a personal account. Claude works with the Fibery rights of the connected person and nothing more: two tools even report those rights, at space and database level and record by record through sharing. With 59 write tools, including permanent deletions, the default approval is worth keeping.
Which plans include it
Of the 819 sheets in the official directory, none shows availability per plan. That connector-by-connector answer is published nowhere: a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can sign in. What your Fibery subscription includes is a separate matter, set by Fibery. For the up-to-date state of this connector, check its sheet in the official directory.
Where the Claude Fibery connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a record changes state or a comment is posted.
Only Fibery documents this connector: no Claude help article covers it, so these limits come from Fibery's user guide, its tool reference and the directory sheet. The tool list is an observed floor, not a promise, since administrators can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic states on each sheet that it neither picks a publisher's tools nor guarantees how they behave. For a connector whose sources disagree on what it may send, compare with the Claude gmail connector.
Need help connecting Fibery to Claude?
A person reads every message.

