Can the AI automatically log time for a specific project?

Yes! Use the `create_timesheet` tool. You'll need to provide the ProjectID, PersonID, and the duration to instantly log work hours in your Avaza account.

How do I update the status of a task through the AI?

Simply ask the agent to run the `update_task` tool with the TaskID. You can modify the title, description, or status to reflect the current progress of your work.

Does this integration allow for auditing recent customer invoices?

Yes. The `list_invoices` tool provides a clear overview of recent billing, helping you track payment statuses and financial health across your projects.

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "avaza": {
      "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 Avaza MCP Server

Connect your Avaza account to any AI agent and manage your entire professional services lifecycle through natural conversation.

GitHub Copilot Agent mode brings Avaza 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.

What you can do

Project & Task Operations — Create, update, and list projects and tasks to keep your team aligned and on schedule
Smart Time Tracking — Log and audit timesheet entries for accurate resource management and billing
CRM & Financial Insights — Access company contacts and retrieve recent invoices for full visibility into project financials
Resource Coordination — Programmatically manage your professional services workflows and team allocations

The Avaza 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 Avaza to VS Code Copilot via MCP

Follow these steps to integrate the Avaza 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 Avaza

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

Why Use VS Code Copilot with the Avaza MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Avaza 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

Avaza + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Avaza 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

Avaza MCP Tools for VS Code Copilot (11)

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

create_project

Create a new project

create_task

Create a new task in a project

create_timesheet

Create a new timesheet entry

get_account_check

Verify Avaza account connection

get_project

Get details for a specific project

list_contacts

List company contacts and users

list_invoices

List recent invoices

list_projects

List all Avaza projects

list_tasks

List all Avaza tasks

list_timesheets

List timesheet entries

update_task

Update an existing task

Example Prompts for Avaza in VS Code Copilot

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

"List all active projects in Avaza."

"Create a new task 'Prepare Financial Audit' in project ID 12345."

"Log 2 hours of work for today on project 'Website Redesign'."

Troubleshooting Avaza MCP Server with VS Code Copilot

Common issues when connecting Avaza 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.

Avaza + VS Code Copilot FAQ

Common questions about integrating Avaza 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.