TextYess MCP Server for CursorGive Cursor instant access to 12 tools to Get Campaign Analytics, Get Campaign Conversions, Get Campaigns Delivery Status, 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 TextYess app connector for Cursor is a standout in the Productivity 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 TextYess and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"textyess": {
"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 TextYess MCP Server
Connect your TextYess account to any AI agent and simplify how you manage your AI-driven sales, WhatsApp marketing campaigns, and conversational commerce analytics through natural conversation.
Cursor's Agent mode turns TextYess into an in-editor superpower. Ask Cursor to generate code using live data from TextYess 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
- Campaign Management — List all WhatsApp marketing campaigns and retrieve detailed analytics including opens, clicks, and revenue.
- Order Tracking — Monitor conversational commerce sales by listing all orders processed through AI agents or campaigns.
- Product Sync Oversight — List and inspect products synced from your e-commerce platform (Shopify, etc.) to your TextYess catalog.
- Agent Interaction Monitoring — List and review recent customer conversations with your AI shopping agent to ensure quality.
- Integration Control — List connected e-commerce platforms and verify active webhooks for product and order sync.
- Organizational Insights — Retrieve metadata for your organization and user profile directly from the agent.
The TextYess 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 TextYess tools available for Cursor
When Cursor connects to TextYess through Vinkius, your AI agent gets direct access to every tool listed below — spanning conversational-commerce, whatsapp-marketing, ai-sales-agent, 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.
Get analytics for a specific campaign
List orders generated by a campaign
Check campaigns deliverability
Get authenticated user profile
Get organization information
Get details for a specific product
List AI agent interactions
List all conversational commerce orders
List active webhooks
List connected e-commerce platforms
List WhatsApp marketing campaigns
List all synced products
Connect TextYess to Cursor via MCP
Follow these steps to wire TextYess 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 TextYess
Why Use Cursor with the TextYess MCP Server
Cursor AI Code Editor provides unique advantages when paired with TextYess 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
TextYess + Cursor Use Cases
Practical scenarios where Cursor combined with the TextYess 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 TextYess in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with TextYess immediately.
"List all active marketing campaigns in my TextYess account."
"Show me the revenue generated by the 'Abandoned Cart' campaign (ID: camp_10293)."
"List the last 3 customer conversations with the AI shopping agent."
Troubleshooting TextYess MCP Server with Cursor
Common issues when connecting TextYess to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
TextYess + Cursor FAQ
Common questions about integrating TextYess 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.