2,500+ MCP servers ready to use
Vinkius

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

Connect your AI agents to Sensors Data (神策数据), the leading professional big data analytics platform. This MCP provides 10 tools to manage event tracking, retrieve user behavioral profiles, and monitor the health of your data pipeline directly through natural conversation.

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

  • Event Orchestration — Query and analyze event metadata and properties to understand user interactions in real-time
  • User Profiling — Retrieve detailed behavioral profiles and attributes for specific user IDs to power personalized experiences
  • Data Health — Monitor ingestion rates and check for data quality issues across your analytics streams
  • Project Management — List and inspect project configurations, including project names and token settings
  • Export Intelligence — Trigger and monitor data export tasks for further downstream processing or reporting

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

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

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

Why Use VS Code Copilot with the Sensors Data MCP Server

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

Sensors Data + VS Code Copilot Use Cases

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

Sensors Data MCP Tools for VS Code Copilot (10)

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

01

analyze_events

Perform complex event analysis

02

analyze_funnel

Calculate conversion funnel metrics

03

analyze_retention

Calculate user retention rates

04

get_event_schema

Retrieve the property schema for a specific event

05

get_project_info

Retrieve Sensors Data project metadata

06

get_user_behavior_sequence

Get the chronological sequence of events for a user

07

list_events

List all defined event names in the schema

08

list_user_properties

List all defined user profile properties

09

lookup_user

Get profile information for a specific user

10

query_behavior_list

Retrieve a list of user behaviors/events

Example Prompts for Sensors Data in VS Code Copilot

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

01

"Show me the top 5 events by volume in project 'MainApp' for today."

02

"Get the behavioral attributes for user ID 'user_sensors_777'."

03

"Is the data ingestion pipeline healthy for project 'AnalyticsBeta'?"

Troubleshooting Sensors Data MCP Server with VS Code Copilot

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

Sensors Data + VS Code Copilot FAQ

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

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