How do I find my Fibery Workspace name?

Your workspace name is the subdomain in your Fibery URL. For example, if you access Fibery at `https://my-team.fibery.io`, your workspace name is `my-team`.

How do I generate a Fibery API Token?

In your Fibery workspace, go to **Settings > API**, click on **Create New Token**, give it a name, and copy the generated token immediately.

Can I query custom fields created in my spaces?

Yes! Use the `get_schema` tool to see the fully qualified names of your custom fields, and then include them in the `select_json` parameter of the `query_entities` tool.

Fibery MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Name: Fibery
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 11 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Fibery and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "fibery": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Fibery MCP Server

Fibery is a work management platform that adapts to your unique processes. This MCP server allows your AI agent to interact with your Fibery workspace seamlessly.

GitHub Copilot Agent mode brings Fibery data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

Key Features

Space & Schema Discovery — List all your spaces (apps) and retrieve the full schema to understand your custom databases and fields.
Entity Management — Query, create, update, and delete entities across any of your custom databases flawlessly.
Comment Integration — Read and add comments to entities to keep your team in sync natively.
Advanced Querying — Use granular filters and field selections to retrieve exactly the data you need synchronously.
Cross-Database Search — Search for information across your entire workspace flawlessly through the agent.

The Fibery MCP Server exposes 11 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fibery to VS Code Copilot via MCP

Follow these steps to integrate the Fibery MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Fibery

Ask Copilot: "Using Fibery, help me..." — 11 tools available

Why Use VS Code Copilot with the Fibery MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Fibery through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Fibery + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Fibery MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Fibery MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect Fibery to VS Code Copilot via MCP:

add_comment

Add a comment to an entity

create_entity

Create a new entity in a specific database

delete_entity

Delete an entity

get_comments

Retrieve comments for a specific entity

get_entity

Get a specific entity by its UUID

get_schema

Retrieve the full schema of the workspace, including all databases (types) and fields

list_apps

List all Fibery apps (spaces)

list_users

List all users in the Fibery workspace

query_entities

Query entities from a specific database (type)

search_entities

Search for entities by keyword across all databases

update_entity

Update an existing entity

Example Prompts for Fibery in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Fibery immediately.

"List all active spaces in my Fibery account."

"Show me the tasks assigned to me in the 'Software Development' space."

"Add a comment to task UUID-123 saying 'The client approved the design'."

Troubleshooting Fibery MCP Server with VS Code Copilot

Common issues when connecting Fibery to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Fibery + VS Code Copilot FAQ

Common questions about integrating Fibery MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.