Bring App Store Optimization
to Cursor
Learn how to connect Google Play Developer to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Google Play Developer MCP Server?
Connect your Google Play Developer account to your AI agent and streamline your Android app management. Use natural language to monitor user reviews, manage subscriptions, and verify in-app purchases directly from your workflow.
What you can do
- Review Management — Fetch recent reviews, read specific feedback, and post replies directly from the chat
- Subscription Tracking — Check the status of user subscriptions, issue refunds, or defer billing dates effortlessly
- In-App Purchases — Verify, acknowledge, and consume in-app product purchases
- Product Catalog — List all available in-app products and retrieve specific SKU details
How it works
1. Subscribe to this server
2. Enter your Google Play App Package Name (e.g. com.example.app)
3. Complete the secure Google OAuth flow with a user that has developer access
4. Start managing your app from Claude, Cursor, or any MCP-compatible client
Who is this for?
- App Developers — quickly acknowledge test purchases or verify subscription states during development
- Customer Support — easily look up a user's subscription or purchase status and issue refunds without opening the Play Console
- Community Managers — draft and post professional replies to Google Play reviews directly through the AI agent
Built-in capabilities (12)
Acknowledge a product purchase
Cancel a user subscription
Consume a product purchase
Defer a subscription billing date
Get details for a specific in-app product
Check an in-app product purchase status
Get a specific review by ID
Check the status of a subscription purchase
List in-app products for the app
List recent user reviews for the app
Refund a subscription
Reply to a user review
Why Cursor?
Cursor's Agent mode turns Google Play Developer into an in-editor superpower. Ask Cursor to generate code using live data from Google Play Developer 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.
- —
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
Google Play Developer in Cursor
Google Play Developer and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Google Play Developer to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Google Play Developer in Cursor
The Google Play Developer 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. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Google Play Developer for Cursor
Every tool call from Cursor to the Google Play Developer MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I reply to user reviews with this integration?
Yes! You can use the reply_to_review tool. Simply provide the Review ID and the text you want to reply with, and the AI agent will post it to the Google Play Store on your behalf.
How do I check if a user's subscription is active?
Use the get_subscription_purchase tool with the Subscription ID (SKU) and the user's purchase token. The AI will return the full status of their subscription.
Can I issue refunds for subscriptions?
Yes, you can use the refund_subscription tool by providing the Subscription ID and the purchase token.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a 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.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.