2,500+ MCP servers ready to use
Vinkius

Amplience 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 Amplience 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": {
    "amplience": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Amplience
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 Amplience MCP Server

Link your Amplience headless CMS to any intelligent AI agent to completely rethink how you handle your enterprise content architecture, deploying components natively through standard conversation.

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

What you can do

  • Discover Asset Hierarchies — Freely list top-level Hubs, target specific Repositories, and fetch internal Folders to help your AI inherently understand where every graphic and article lives.
  • Content Retrieval — Paginate through dynamic content items, safely extracting complete metadata alongside current active schemas and validation rules.
  • Edit & Create Structure — Give the agent full permission to push correctly strictly-typed JSON payloads back into the system, generating or modifying blog entries and product metadata.
  • Manage Deployments — Permanently execute deletions (if revision locks permit) or instruct the system to fire a specific content configuration directly over to the edge delivery API to hit the live website.

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

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

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

Why Use VS Code Copilot with the Amplience MCP Server

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

Amplience + VS Code Copilot Use Cases

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

Amplience MCP Tools for VS Code Copilot (10)

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

01

create_content_item

Create a new structured content item adhering to a schema inside a folder

02

delete_content_item

Requires version validation before deletion. Permanently delete a content item from the repository database

03

get_content_item

Retrieve a specific content item configuration and its schema revision lock

04

get_delivery_content

Retrieve the exact structural matching verifying Delivery CDN blocks

05

list_content_items

Retrieve paginated content items from a specific repository

06

list_folders

List all folders organizing content in a given repository

07

list_hubs

Essential for retrieving the active workspace. List all accessible Amplience Hubs (environments)

08

list_repositories

List all content repositories within a specific Hub

09

publish_content_item

Publish a specific content item version to the live delivery CDN

10

update_content_item

Update an existing content item data structure matching its current schema

Example Prompts for Amplience in VS Code Copilot

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

01

"Identify all active repositories present inside my default Amplience Hub."

02

"Pull the structural metadata (schema lock and payload) of item '5tYv92'."

03

"Publish the newly edited Content '5tYv92' to the global live network."

Troubleshooting Amplience MCP Server with VS Code Copilot

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

Amplience + VS Code Copilot FAQ

Common questions about integrating Amplience 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 Amplience to VS Code Copilot

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