2,500+ MCP servers ready to use
Vinkius

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

Connect your Phyllo developer integration to any AI agent and track creator analytics cleanly across dozens of social networks concurrently via natural workflow prompts.

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

  • Audience Deep Dives — Query massive, accurate demographics, historical subscriber growth models, and active platform footprints for individual global influencers
  • Campaign Tracking — Automatically correlate real-time engagement data on live influencer posts scaling directly across YouTube, TikTok, and Instagram
  • Content Aggregation — Ingest raw video and post performance metadata directly into analytical AI arrays
  • Identity Verification — Verify social reach legitimately via first-party authenticated account details directly queried from major providers safely

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

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

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

Why Use VS Code Copilot with the Phyllo MCP Server

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

Phyllo + VS Code Copilot Use Cases

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

Phyllo MCP Tools for VS Code Copilot (10)

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

01

create_connect_session

Generate a secure Connect session token

02

get_account_income

Fetch verified income streams linked to the creator account

03

get_creator_audience

Get detailed demographic info about a creators audience

04

get_creator_content

Retrieve recent posts, videos, or streams from a creator

05

get_creator_profile

Get a unified creator profile across platforms

06

get_engagement_stats

Get engagement analytics for a specific piece of content

07

get_identity_status

Check if a creator has verified their real-world identity

08

get_platform_list

List all social platforms supported by Phyllo

09

get_webhook_status

Check the status and configuration of registered webhooks

10

search_creators

Search for creators across supported social platforms

Example Prompts for Phyllo in VS Code Copilot

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

01

"Provide the complete 3-month growth insights for the creator linked to 'uid-9430'."

02

"List all active posts sponsored by brand XYZ published in the last 48 hours."

03

"Rank our top 10 verified fitness creators based solely on Instagram comment-to-follower ratio."

Troubleshooting Phyllo MCP Server with VS Code Copilot

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

Phyllo + VS Code Copilot FAQ

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

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