How to Use the Instamojo MCP in Windsurf

Q: How do I connect the Instamojo server to Windsurf?

Open your mcpconfig.json file in Windsurf and paste the server configuration. Once connected to the MCP Server, Windsurf auto-discovers the payment tools, allowing Cascade to start running queries immediately.

Q: Can Windsurf autonomously issue refunds via Instamojo?

No, this server only reads refund data. Windsurf uses listrefunds and getrefund to pull status updates and transaction histories, meaning Cascade cannot move funds or execute new refunds on its own.

Q: How does Windsurf map Instamojo payouts to my local database?

Cascade uses listpayouts to get bank transfer details, then inspects your local database to match transaction IDs. It writes the SQL queries and runs them to sync your ledger with real-world bank drops.

Let Windsurf autonomously pull payment records, resolve disputes, and track payouts directly inside your workspace.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Instamojo MCP to Windsurf

Create your Vinkius account to connect Instamojo to Windsurf and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Instamojo with Windsurf

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Track payments autonomously with Windsurf

This MCP Server lets Windsurf check your cash flow using `list_payments` and `get_payment` without you writing a single line of API boilerplate. Cascade reviews your local database schema, matches it with your live transaction records, and updates your accounting ledger in one continuous run. Instead of asking you for confirmation at every step, your agent pulls the transaction ID, grabs the exact payout breakdown via `list_payouts`, and logs the net settlement. You set the goal of balancing today's books, and Cascade handles the multi-step API calls to map every cent.

Auto-manage buyer disputes inside Windsurf

This MCP Server exposes `list_disputes` to let your agent scan for payment conflicts before they turn into chargebacks. Cascade flags incoming disputes, cross-references the matching transaction ID using `get_payment_request`, and drafts your internal response notes instantly. You don't have to jump between browser tabs to hunt down what went wrong. Windsurf takes the customer's email from your support log, finds their payment link with `list_links`, and tells you exactly which transaction needs attention.

Handle refunds directly from Cascade

This MCP Server provides `list_refunds` and `get_refund` so Windsurf can track returned customer funds without leaving the editor. Cascade checks the status of a disputed transaction, confirms the original amount, and logs the refund reference number. If a customer requests a return, you simply tell Cascade to verify their claim. Your agent calls `get_payment` to verify the original purchase, traces the refund path, and updates your local support tickets automatically.

Setup guide

Set up Instamojo MCP in Windsurf

Prerequisites

Windsurf IDE installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Click the Cascade assistant icon in the sidebar, then click the hammer icon (🔨) at the top of the panel. Select "Configure" to open ~/.codeium/windsurf/mcp_config.json.
2

Add the Instamojo MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Refresh MCPs

Go back to the hammer icon (🔨) in Cascade and click "Refresh". Windsurf will detect the new server. No full restart is needed — the connection is hot-reloaded.
4

Verify in Cascade

Start a new Cascade conversation and ask something like "Show my Instamojo payment history." If connected, Cascade will call the Instamojo tools directly. You will see a green dot next to the server name in the MCP panel.

mcp_config.json

{
  "mcpServers": {
    "instamojo-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Instamojo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Instamojo now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Instamojo MCP in Windsurf

Open your `mcp_config.json` file in Windsurf and paste the server configuration. Once connected to the MCP Server, Windsurf auto-discovers the payment tools, allowing Cascade to start running queries immediately.

No, this server only reads refund data. Windsurf uses `list_refunds` and `get_refund` to pull status updates and transaction histories, meaning Cascade cannot move funds or execute new refunds on its own.

Cascade uses `list_payouts` to get bank transfer details, then inspects your local database to match transaction IDs. It writes the SQL queries and runs them to sync your ledger with real-world bank drops.

No, Cascade runs autonomously. It uses the MCP Server to call `list_disputes` to check for active complaints and matches them against `list_payment_requests` to identify the source of the issue without prompting you for permission.

Yes, your transaction records, payout details, and dispute histories never touch third-party servers. All API requests run locally inside your sandbox using your direct API keys, meaning your payment logs remain private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript