MCP server tools

Overview of Fibery MCP Server tools.

This page lists tools by category with short descriptions. For parameters, value formats, and examples, see the MCP tool reference.

Tools by category

Explore your workspace

Tool	Description
schema	Lists every space and database in the workspace. The AI calls this first to know what exists.
schema_detailed	Zooms into a specific database and shows all its fields, types, and possible values (e.g. workflow states).
get_me	Returns the currently logged-in user’s name, email, and ID.
search_guide	Searches the official Fibery documentation to answer questions about how Fibery works.

Search and query

Tool	Description
query	The main read tool. Fetches entities from any database with filtering, sorting, and pagination. Supports sub-queries.
search	Full-text keyword search across the entire workspace — entity names, document content, and comments.
search_history	Looks up the activity log: what was created, updated, or deleted, by whom, and when.
query_views	Lists saved views (boards, timelines, grids, documents, etc.) and their configuration.
fetch_view_data	Executes a saved view and returns the actual entities it would show, with the view’s own filters applied.

Create and update entities

Tool	Description
create_entities	Creates one or more new entities in a database.
update_entities	Updates fields on existing entities. Only the fields you specify are changed.
delete_entities	Permanently deletes entities. Cannot be undone.
set_state	Moves an entity to a different workflow state.
get_entity_links	Returns direct Fibery web links to entities by their public IDs.
add_collection_items	Adds items to a collection field: assign a person, attach a tag, link a related entity.
remove_collection_items	Removes items from a collection field.

Documents and files

Tool	Description
get_documents_content	Reads the rich-text document content of an entity field and returns it as readable text.
set_document_content	Writes or replaces the document content of an entity field.
append_document_content	Adds content to the end of an existing document without replacing what’s already there.
add_file_from_url	Downloads a file from a URL and attaches it to an entity’s file field.

Structure (spaces, databases, fields)

Tool	Description
create_space / delete_space	Creates or removes a top-level space.
create_databases / rename_databases / delete_databases	Manages databases within a space.
create_primitive_fields	Adds simple fields: text, number, date, date range, checkbox, URL, email, phone, location, or rich-text document.
create_relation_fields	Creates a link between two databases with a chosen cardinality.
create_single_select_fields / update_single_select_fields	Creates or modifies a single-choice dropdown field.
create_multi_select_fields / update_multi_select_fields	Creates or modifies a multi-choice tag-style field.
create_workflow_field / update_workflow_field / delete_workflow_field	Manages the workflow (state) field: defines stages and their types.
create_formula_field / update_formula_field	Creates or updates a calculated field. Describe what it should compute in plain English.
rename_fields / delete_fields	Renames or removes fields from a database.
create_comments_fields / delete_comments_fields	Enables or disables comments on entities.
create_avatars_fields / delete_avatars_fields	Enables or disables avatar images on entities.
create_icon_fields / delete_icon_fields	Enables or disables emoji icons on entities.
create_files_fields	Adds a file attachment field to a database.

Views

Tool	Description
create_view	Creates a new view: board, grid, timeline, calendar, gantt, gallery, map, feed, form, or standalone document.
update_view	Edits an existing view’s name, config, or content.
delete_views	Removes views (entity data is not affected).

Import

Tool	Description
get_connectors_list	Lists all available built-in integrations (Trello, Notion, Jira, CSV, etc.).
get_import_link	Generates a URL to the Fibery import wizard for a specific connector and target database.

Use cases

Each use case shows a natural prompt, the tools called behind the scenes, and what comes back.

Find things

Prompt	Tools	Result
”Show me all urgent bugs that aren’t done yet”	schema_detailed → query	Table of urgent bugs with name, state, and assignee
”What did the team work on this week?”	search_history	Chronological feed of every entity created or updated in the last 7 days
”Find everything related to inline comments”	search	Ranked list of matching bugs, features, customer requests, and documents
”Give me a full picture of the history migration feature”	query → get_documents_content → query	Feature state, owner, planned dates, linked open bugs, and the full description
”Who has the most open bugs assigned to them?”	schema_detailed → query	Team members ranked by open bug count
”Which Icebox features have the highest customer demand?”	schema_detailed → query → get_entity_links	Features sorted by Highlights Score descending, with direct links

Create and update things

Prompt	Tools	Result
”Create a bug: form fields lose their value when switching tabs. Assign it to Nastya and mark urgent.”	schema_detailed → create_entities → add_collection_items → update_entities	Bug created, assigned, and marked urgent with a confirmation link
”Move all Implemented features to Done”	schema_detailed → query → set_state	All matching features transitioned
”Write a structured description for the inline comment icons bug”	search → query → set_document_content	Description written with Summary, Steps to Reproduce, Expected vs. Actual sections
”Add a Severity field to bugs — Critical, High, Medium, Low”	schema → create_single_select_fields	Severity field created with four color-coded options
”Link this customer request to the Figma plugin feature”	search → query → add_collection_items	Request linked to feature; both entities now reference each other
”Set up a new Design space with task tracking linked to features”	create_space → create_databases → create_workflow_field → create_primitive_fields → create_relation_fields	Space created with databases, workflow, fields, and relations

Multi-step workflows

Prompt	Tools	Result
”Prepare my standup — what did I do yesterday and what’s stuck?”	get_me → search_history → query	Yesterday’s activity, current in-progress items, and items flagged as at risk
”Audit features with no owner and no planned dates”	schema_detailed → query → get_entity_links	Features missing owner or dates, grouped by gap type, with direct links
”Write this week’s release notes from what shipped”	search_history → get_documents_content → append_document_content	New dated section appended to Release Notes with every completed item
”Triage new customer requests — match each to the right feature”	query → get_documents_content → add_collection_items → set_state	Requests matched to features and moved to In Review; unmatched ones flagged
”Sprint health report — what’s at risk?”	query_views → fetch_view_data → search_history → get_entity_links	Items by state, items with no recent activity flagged, overdue items highlighted