May 14, 2026 / Bullet and checklist improvements, MCP Server improvements

[mdubakov]

Bullet and checklist improvements

We’ve fixed many problems with bullet lists and checklists in this release, including tabs behavior, list items deletion, etc. Moreover, you can mix bullet lists and checklists freely.

MCP Server improvements

We’ve improved quality of almost all Fibery MCP Server tools. We discovered that some tools were not reliable and produced a lot of mistakes. Most AI agents had to do several tries to get them work. In this release all MCP tools are more reliable.

Here is the list of improvements for the tools:

• query. Fixed a range of errors that caused failed queries.
• fetchByUrl. Clearer error messages when a URL is invalid, especially when it points to a different Fibery workspace.
• createView. Moved detailed view configuration docs into a separate reference that the AI fetches on demand. Creating non-trivial views now takes one extra step but succeeds far more reliably.
• createEntities. Streamlined the main description by moving rarely-used field types (like location) into a reference doc.
• searchHistory. Shorter, sharper description so the AI can actually see it. Also fixed the 12-month limit being invisible to the model, it’s now respected.
• update_workflow_field. Fixed a crash when renaming the workflow field
• add_file_from_url. Now explicitly states the URL must be publicly accessible, so the model stops guessing.
• create_primitive_fields — Boolean and Document fields no longer silently drop their description, which was causing field creation to be rejected as incomplete. Also fixed a few common mistakes around meta flags and missing database references.

Add Comment command

Add Comment command is added, so you can add new comments (or replies) to entities via MCP now.

NOTE: it’s not possible to add inline comments in rich text so far.

Even more icons for your Whiteboard

We’ve added three new icon packs to give your whiteboards more personality:

• Bootstrap: clean UI icon set
• Phosphor Regular and Fill: modern icon set in outline and filled styles

More icons means more ways to organize and personalize your boards.

Redesigned Database Data header

We’ve redesigned the Database header to make navigation clearer and help users work with data more effectively. The updated header better distinguishes database configuration from actual data work, highlights Views more prominently, and makes it easier to access, create, and manage Views directly from the header.

Key changes:

• Clearer Database title with icon and quick rename (simply click on Database name to edit it and set color)
• New “Database Preview” badge with entity count and 500-entity limit awareness
• Views are now easier to access and create via the new “Views” button
• More consistent menus, including Import / Sync actions and a unified Fields menu structure

Improvements

• Entity View. It’s now easier to spot Entities from Integration Databases — an integration icon is shown next to the database badge in the page header.
• Desktop app. Now you can select Home page option in the Default new tab setting.

Fixed Bugs

• Bullet/Number/Checklist in rich text:
  • Tab key doesn’t indent an item in a list when a checkbox is above
  • Loosing focus in rich-text if try to add wrong hierarchy level to numeric or bulleted list
  • Copy-paste checklists into other apps works bad
  • You can’t delete a nested checkbox line and keep the nested level
  • Deleting issue in check list
  • Issue with editing pasted bulleted list, moving to nested level by Tab does not work
  • It’s impossible to format bulleted/numeric or checklist to callout
  • H1/H2/ header fails to be collapsed when cursor is in bulleted list and user needs to scroll up to access the header
  • Hierarchy does not get saved on converting check-boxes to bullet or ordered list
  • It’s impossible to change list to checkbox and back if it’s placed in the table cell
• Documents / Rich Text:
  • Text formatting is lost after typing ‘/’ or mentioning an entity
  • Formatting settings do not apply in the Code block
  • Text formatting toolbar does not get hidden on click out
  • When backspacing in a heading block, if I remove the final character, the page scrolls/jumps up a little
  • Same comment is duplicated in Unlinked and Open tabs after converting line from list to check-box
• Table View: Database name is not added to some related field title when export table to CSV
• Related units: Hide the Fields menu item if relation value is empty
• Colors: Select background doesn’t look good with close color coding
• Sidebar: Folders fail to be moved from My Space ( Private) to regular space AND ‘Move to space’ option is missed in ‘…’ menu
• Form View:
  • Context selector is missed in Form when create entity in Table relation views with indirect context filters and related collections
  • Default form doesn’t appear when select Create option when link or create entities in relation list
• Performance: Application memory grows unboundedly on object editor screen if user modifies schema many times
• Whiteboard:
  • The text color is applied to the cursor which makes the cursor is hardly visible
  • Shape size gets collapsed when it’s pasted near top or left whiteboard border

P.S. We are working on Fibery Apps, and need your input to make some sane decisions. Thank you for the help!

[Lee_Denny]

Nice to see some more MCP improvements but still missing some key abilities which block a lot of work:

• Manage Permissions
• Access Files
• Create Proper Backlinks

Could you let us know when those will be available?

[timothy]

Thanks for all of this — especially the MCP improvements and “Default form doesn’t appear when select Create option when link or create entities in relation list” — this solved a major problem for us

[Jess_Bachman]

If the MCP could see/edit the automations that would be ideal. I always have to walk claude through those myself.

[mdubakov]

@Jess_Bachman

If the MCP could see/edit the automations that would be ideal

We are working on that now

[mdubakov]

@Lee_Denny

• Manage Permissions
• Access Files
• Create Proper Backlinks

Know permissions — quite soon. Manage permissions — maybe several months away
Access files — quite soon
Create proper backlinks — hard to say so far, maybe will be a part of partial rich text updates

[interr0bangr]

@mdubakov

Fixed Bugs

@mdubakov

Context selector is missed in Form when create entity in Table relation views with indirect context filters and related collections

Could you elaborate/clarify on this? I still don’t really understand why known related entities within in the form interface can’t be used in relation filters. It makes me want to pull my hair out every single day.

Your own page here says that relation filters work in forms, but I have never been able to get them to work. Fibery

If it’s because the related entity is “not accessible”, then why is the “-> is x entity” filter even an option in forms? In what scenario would a form ever not display the “missing dynamic values” error? What even is a relation filter in forms if it can’t filter on related entities?

[Chr1sG]

@interr0bangr

What even is a relation filter in forms if it can’t filter on related entities?

A ‘relation filter’ is a filter applied to a relation, i.e. limit the possible options to choose from for the item that should be related.

I can create a relation filter to say “Only allow items to be related if they are in the Done state”

I think what you’re primarily talking about is ‘dynamic’ relation filters. A dynamic relation filter is one where the filter is not fixed (static) but depends upon the entity to which things are being related.

A dynamic relation filter could be “Only allow items to be related if they belong to the project which this item is related to”.

When an item hasn’t been created yet (e.g. using a form view) these dynamic filters can’t be applied. For the example above - “Only allow items to be related if they belong to the project which this item is related to” - the problem is that this item* does not yet have any meaning.

Now, of course, from the point of view of the user, there is the intention to create an item which links to a specific project (because that field has already been populated in the form).
Unfortunately, the technical mechanism by which relation filters work isn’t aware of that…until the item is actually created.

We do plan on fixing this, but I hope that explains the terminology and behaviour.

[Chr1sG]

@interr0bangr

why is the “-> is x entity” filter even an option in forms?

A relation filter that is created in one place is present in all the places where that relation drop-down exists. This means a dynamic relation filter can be created in one place (entity view) and work for existing entities, but then not work when it shows up in other places (form view).

[christamae]

Everyone’s excited about the MCP improvements, but I’m rejoicing about the attention RichText fields are getting

[mdubakov]

In general we are stopping here
Nest possible feature is Suggestions mode and we will pause rich text improvements for now.

[tycecycle]

Nest possible feature is Suggestions mode

yesssssssssss

also for others looking forward to this A "suggesting" mode for document editing (i.e. multiple document editing "roles")