Integration

Instamojo integration

Instamojo is an Indian payments platform. With its v2 Payments API an agent can create a payment request (a payment link for an amount and purpose, optionally emailed to the buyer), read a payment request and the payments made on it, read a payment's status, instrument, fees and failure reason, refund a payment (one refund per payment, full or partial) and follow the refund case. Not exposed: the payments list (its response is not documented), the SDK-only order route, and the token route (the platform fetches tokens itself); buyer shipping addresses and the webhook URL are not returned. Authentication is application based: the Client ID and Client Secret shown on the Instamojo integrations page (www.instamojo.com/integrations) are exchanged for a bearer token with the client_credentials grant. These are production credentials; sandbox credentials from test.instamojo.com do not work here.

Connect Instamojo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Instamojo.Built from the 5 Instamojo tools below, on the connection you add once.

What you can do with Instamojo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Payment request, 2 operations

create_payment_requestCreate payment requestPOSTCreates a payment request and returns its payment link (longurl) to share with the buyer; nothing is charged until the buyer pays. With send_email=true Instamojo emails the link to the buyer for real.
get_payment_requestGet payment requestGETReturns one payment request: amount, purpose, buyer, status (Pending, Sent, Failed, Completed), its payment link and the links of payments made on it. Completed means a customer paid.

Refund, 2 operations

create_refundCreate refundPOSTRefunds a payment for real by opening a refund case; money goes back to the buyer. Only one refund per payment is supported. Leave refund_amount out to refund the full amount paid.
get_refund_caseGet refund caseGETReturns one refund case: its resolution_status (null while open, FINI_CONC refunded, FINI_DENY resolved, FINI_WITH cancelled, FINI_INIT closed), amount, reason and the refund transfers with bank reference numbers.

Payment, 1 operation

get_paymentGet paymentGETReturns one payment: status (true successful, false failed, null initiated), amount, currency, buyer, instrument, Instamojo fees and taxes, the failure reason when it failed, and its payment request.

Use Instamojo from Claude Code, Cursor or Codex

Connect Instamojo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Instamojo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Instamojo

Create your workspace
Sign up free. Nothing to install.
Connect Instamojo once
Add your Instamojo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.