Overview

​

What is Fibery MCP Server?

The Fibery MCP Server connects AI assistants to your Fibery workspace via the Model Context Protocol. Once connected, your AI assistant can query databases, manage entities, run searches, and even modify your workspace schema — all through natural language. To set up the Fibery MCP Server in your AI client, see Connecting to Fibery MCP.

​

What the Fibery MCP Server can do

​

Read operations

• Explore workspace structure — Discover spaces, databases, and fields
• Query databases — Filter, sort, and paginate any database
• Full-text search — Search across all content in the workspace
• Activity history — See who changed what, and when
• Retrieve view data — Pull data from saved views as configured

​

Write operations

• Manage entities — Create, update, and delete entities
• Workflow management — Move entities through workflow states
• Assignments and links — Assign users and link related records
• Rich-text documents — Read and write entity descriptions and documents
• File attachments — Attach files to records by fetching from a URL

​

Schema modifications

• Spaces and databases — Create and delete spaces and databases
• Fields — Add fields of any type: text, number, date, dropdown, relation, formula
• Workflow stages — Configure workflow states
• Views — Create and update boards, timelines, calendars, and forms

For a full list of available tools, see the tools reference.

​

Example prompts

These examples show the kinds of requests your AI assistant can handle once connected: Querying and reporting

• “Show me all urgent bugs that aren’t done yet.”
• “What did team X work on this week?”
• “Who has the most open bugs assigned to them right now?”
• “Which Icebox features have the highest customer demand?”
• “Give me a sprint health report — what’s at risk and what’s overdue?”
• “Write this week’s release notes from everything that shipped.”

Entity detail and context

• “Give me a full picture of feature X — state, owner, linked bugs, description.”
• “Prepare my standup — what did I work on yesterday and what’s stuck?”
• “Find all bugs that have been In Progress for more than a week with no updates.”

Creating and updating

• “Create a bug: form fields lose their value when switching tabs. Assign it to Nastya and mark it urgent.”
• “Move all Implemented features to Done.”
• “Link this customer request to the Figma plugin feature.”
• “Triage new customer requests — match each one to the most relevant feature.”

Schema changes

• “Add a Severity field to bugs — Critical, High, Medium, Low.”
• “Set up a new Design space with task tracking linked to features.”

​

FAQ