Fibery MCP connector for AI agents

Tools your project management agent reaches for on Fibery MCP, scoped per user.

CALL ANY TOOL

Each tool maps to a core Fibery operation — querying relational entities, creating records, updating fields, and managing documents — all resolved under the authorizing user's token.

fiberymcp_add_collection_items

Add Collection Items

Adds related entities to a Collection field on a Fibery entity.

Parameters

Name

Type

Required

Description

database

string

Required

Full database name (e.g., 'SoftDev/Task')

entityId

string

Required

fibery/id of an entity

field

string

Required

The name of the collection field

items

array

Required

An array of related entity ids to add to the collection. Each entry must be fibery/id of the entity to add

fiberymcp_add_comment

Add Comment

fiberymcp_add_file_from_url

Add File From Url

fiberymcp_append_document_content

Append Document Content

fiberymcp_create_avatars_fields

Create Avatars Fields

fiberymcp_create_comments_fields

Create Comments Fields

fiberymcp_create_databases

Create Databases

fiberymcp_create_entities

Create Entities

fiberymcp_create_files_fields

Create Files Fields

fiberymcp_create_formula_field

Create Formula Field

fiberymcp_create_icon_fields

Create Icon Fields

fiberymcp_create_multi_select_fields

Create Multi Select Fields

fiberymcp_create_primitive_fields

Create Primitive Fields

fiberymcp_create_relation_fields

Create Relation Fields

fiberymcp_create_single_select_fields

Create Single Select Fields

fiberymcp_create_space

Create Space

fiberymcp_create_view

Create View

fiberymcp_create_workflow_field

Create Workflow Field

fiberymcp_delete_avatars_fields

Delete Avatars Fields

fiberymcp_delete_comments_fields

Delete Comments Fields

fiberymcp_delete_databases

Delete Databases

fiberymcp_delete_entities

Delete Entities

fiberymcp_delete_fields

Delete Fields

fiberymcp_delete_icon_fields

Delete Icon Fields

fiberymcp_delete_space

Delete Space

fiberymcp_delete_views

Delete Views

fiberymcp_delete_workflow_field

Delete Workflow Field

fiberymcp_download_file

Download File

fiberymcp_fetch_by_url

Fetch By Url

fiberymcp_fetch_view_data

Fetch View Data

For more tools, view docs.

Build your Agent

The same per-user token pattern works across LangChain, OpenAI, Anthropic, and Google ADK — no auth code changes per framework.

Try these prompts

Paste any prompt into your agent to get started with Fibery.

Status and triage

Copy the prompt

Copied

What tasks in the product backlog are overdue and unassigned?

Copy the prompt

Copied

Show me everything assigned to me that's due this week.

Copy the prompt

Copied

Which bugs in the current sprint haven't been updated in 3 days?

Copy the prompt

Copied

List all open tasks across spaces where priority is high.

Create and update

Copy the prompt

Copied

Create a new feature request in the Product space titled '[title]' with description '[desc]'.

Copy the prompt

Copied

Mark the task '[task name]' as done and add a comment summarizing what was completed.

Copy the prompt

Copied

Update the priority of all unassigned bugs in the current sprint to High.

Search and summarize

Copy the prompt

Copied

Summarize all meeting notes created this week across the team's spaces.

Copy the prompt

Copied

Find everything related to the '[project name]' initiative and give me a status summary.

Copy the prompt

Copied

List all entities linked to the goal '[goal name]' and show their current status.

SEE HOW AUTH WORKS

The user authorizes once via API key. Every subsequent agent call resolves their token from the vault and enforces scope before the tool executes.

Authorize

Your user connects

Fibery MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Fibery MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Fibery MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Fibery MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern applied to Notion, Asana, Jira, and 100+ other connectors.

ENGINEERING

Engineering standup agent

Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.

ENGINEERING

Auto-release notes agent

Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.

GitHub

View agent

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Most connector libraries treat auth as a demo afterthought — a single shared key that works until it doesn't.

01.

Shared tokens break per-user analytics

A shared API key looks fine in a demo. In production every Fibery write looks like a service account. You lose attribution, audit trails become useless, and compliance reviews fail. Scalekit resolves the real user credential on every call.

// shared token
fibery_entity_create → bot_service_account
audit: who updated this? unknown

// scalekit
fibery_entity_create → user_alice ✓
audit: alice@acme.com, 14:32 UTC

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Fibery MCP today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does each user need their own Fibery API key, or can I share one key across all users?

Each user needs their own API key. Scalekit stores a separate credential per user in an AES-256 vault and resolves the right key at request time. Sharing a single key collapses per-user attribution and breaks audit trails — every Fibery action appears as a single service account regardless of who triggered it.

How are API keys stored and protected?

Keys are encrypted at rest using AES-256 and stored in Scalekit's vault, namespaced per tenant. They are never written to logs, never passed through LLM context, and never exposed in tool call parameters. Keys are decrypted only at the moment the tool executes and passed directly to the Fibery API.

Can I restrict which Fibery tools a given user or agent is allowed to call?

Yes. Scalekit's listScopedTools API returns only the tools permitted for the authenticated user in the current session. You can configure scope at the connector level, the user level, or the tenant level. Tools outside the granted scope return a 403 before the Fibery API is ever contacted.

What happens when a user revokes their Fibery API key or their account is deactivated?

The next tool call that attempts to resolve that user's credential will fail with an auth error. Scalekit surfaces this as a structured error your agent can handle — typically by prompting the user to re-authorize. No other user's credentials are affected, and the revoked key is purged from the vault.

Fibery organizes data as interconnected spaces and types. Does the connector handle relational queries across multiple entity types?

Yes. The fibery_entities_query tool accepts a filter object that can traverse Fibery's relational graph — for example, querying Tasks linked to a specific Goal or Feature. Scalekit passes the filter through to the Fibery API under the authorizing user's token, so relation traversal respects that user's workspace permissions.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit