2,500+ MCP servers ready to use
Vinkius

Jibble MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 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.

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 Jibble and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "jibble": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Jibble
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 Jibble MCP Server

Empower your AI agents with Jibble's time tracking and attendance platform. This MCP server allows you to list time entries, retrieve person details, track activities and projects, and view organization information directly through the Jibble API. Ideal for automating workforce management and productivity analysis.

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

The Jibble MCP Server exposes 10 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 Jibble to VS Code Copilot via MCP

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Jibble

Ask Copilot: "Using Jibble, help me...". 10 tools available

Why Use VS Code Copilot with the Jibble MCP Server

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

01

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

02

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

03

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

04

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

Jibble + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Jibble MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Jibble to VS Code Copilot via MCP:

01

get_organization

Use to verify account-wide configuration. Retrieves organization details

02

get_person

Essential for detailed HR analysis of an individual team member. Retrieves details for a specific person

03

get_time_entry

Returns location data, activity notes, and associated device info. Use for auditing or correcting a specific employee time log. Retrieves details for a specific time entry

04

list_activities

g., "Meeting", "Development", "Break") that employees can select when clocking in. Useful for identifying high-level task categories. Lists all configured activities

05

list_clients

Useful for professional services tracking and billable hours auditing. Lists all configured clients

06

list_groups

g., "Sales Team", "Remote Workers") used to organize the workforce. Useful for group-based performance reporting. Lists all configured groups

07

list_locations

Useful for auditing site-based workforce distribution. Lists all configured locations

08

list_people

Includes names, emails, and internal IDs. Use this to identify personnel before querying their time entries. Lists all people in the organization

09

list_projects

Use this when the user asks for a project-based time breakdown. Lists all configured projects

10

list_time_entries

Returns employee IDs, entry times, and durations. Use this to monitor workforce activity and total work hours. Lists all time entries

Example Prompts for Jibble in VS Code Copilot

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

01

"List all people in my Jibble organization."

02

"Show me the recent time entries."

03

"What are the active projects in Jibble?"

Troubleshooting Jibble MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Jibble + VS Code Copilot FAQ

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

01

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.
02

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.
03

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.
04

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.

Connect Jibble to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.