How do I find my Facebook Page ID?

Go to your Facebook Page, click **About** > **Page Transparency**, and you will find your Page ID there. Alternatively, it is available in your **Meta Business Suite** settings.

Can the agent send messages to any Facebook user?

The agent can only send messages to users who have previously messaged your Page (generating a PSID). This is consistent with Meta's developer policies for enterprise messaging.

Is it possible to retrieve full message history via the agent?

Yes. Use the `get_messages` tool providing the Conversation ID. Your agent will retrieve the history, including content and timestamps for all messages in that thread.

Messenger MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Name: Messenger
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 8 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 Messenger and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "messenger": {
      "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 Messenger MCP Server

Empower your AI agent to orchestrate your entire mobile communication strategy on Facebook Messenger, the leading platform for social engagement. By connecting Messenger to your agent, you transform enterprise messaging into a natural conversation. Your agent can instantly list your conversations, audit message history, and send replies without you ever touching a complex Meta dashboard. Whether you are providing customer support or managing brand personas, your agent acts as a real-time communication assistant, ensuring your Page is always responsive and your community data is organized.

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

What you can do

Conversation Auditing — List all active conversations for your Page and retrieve detailed message history including timestamps.
Messaging Intelligence — Send direct text replies to users instantly to maintain a high response rate.
Persona Oversight — List and retrieve information for brand personas to ensure your bot's identity is correctly applied.
Page Governance — Monitor Page settings and info to maintain strict organizational control over your brand presence.
Content Insights — List message creatives to ensure your automated responses are using the correct media assets.

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

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

Ask Copilot: "Using Messenger, help me...". 8 tools available

Why Use VS Code Copilot with the Messenger MCP Server

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

Messenger + VS Code Copilot Use Cases

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

Messenger MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect Messenger to VS Code Copilot via MCP:

get_messages

Get message history for a specific conversation

get_page_info

Get basic information about the connected Facebook Page

get_page_settings

Get settings for the Facebook Page

get_persona_info

Get details for a specific persona

list_conversations

List recent Messenger conversations for the page

list_message_creative

List message creatives for the page

list_personas

List all personas for the page

send_message

Send a text message reply to a recipient

Example Prompts for Messenger in VS Code Copilot

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

"List all active Messenger conversations for my Page."

"Send 'Thank you for contacting us!' to recipient ID 12345678."

"Show me the message history for conversation t_xxxx."

Troubleshooting Messenger MCP Server with VS Code Copilot

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

Messenger + VS Code Copilot FAQ

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