Tubular MCP Server for CursorGive Cursor instant access to 12 tools to Check Api Health, Get Api Rate Limits, Get Audience Overlap, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Tubular app connector for Cursor is a standout in the Data Analytics category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Tubular and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"tubular": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 Tubular MCP Server
Connect your Tubular Labs video intelligence account to any AI agent and simplify how you analyze digital video trends, creator performance, and cross-platform audience metrics through natural conversation.
Cursor's Agent mode turns Tubular into an in-editor superpower. Ask Cursor to generate code using live data from Tubular and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Video Insights — Retrieve detailed performance metrics and trending data for individual videos or categories across social platforms.
- Creator Intelligence — Search for creators and fetch high-level performance summaries, trends, and audience ratings.
- Audience Demographics — Analyze audience breakdowns (age, gender, location) for specific videos or creators to refine your targeting.
- Sponsorship Tracking — List brand sponsors and monitor sponsored video campaigns to understand the competitive landscape.
- Audience Overlap — Analyze shared audience between two creators or content properties to identify partnership opportunities.
- Operational Monitoring — Check API health and rate limits to ensure your intelligence engine is always running.
The Tubular MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 Tubular tools available for Cursor
When Cursor connects to Tubular through Vinkius, your AI agent gets direct access to every tool listed below — spanning video-intelligence, audience-insights, competitive-benchmarking, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Check API health status
Get current API rate limits
Analyze shared audience between entities
Get reach and engagement ratings
Get summary for a specific creator
Get trends for a specific creator
) for a specific video. Get audience demographics for a video
Get insights for a specific video
List trending videos
List sponsored video campaigns
List sponsors and brand partners
g., name or keywords). Search for creators
Connect Tubular to Cursor via MCP
Follow these steps to wire Tubular into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Tubular
Why Use Cursor with the Tubular MCP Server
Cursor AI Code Editor provides unique advantages when paired with Tubular through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Tubular + Cursor Use Cases
Practical scenarios where Cursor combined with the Tubular MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Tubular in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Tubular immediately.
"Search for top gaming creators in my region."
"Show me the audience overlap between creator 'A-101' and 'B-552'."
"List all active sponsored video campaigns from 'TechBrand Inc'."
Troubleshooting Tubular MCP Server with Cursor
Common issues when connecting Tubular to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Tubular + Cursor FAQ
Common questions about integrating Tubular MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.