Koskamo

Nityaflow MCP

Nityaflow MCP enables AI assistants to build WhatsApp, Sheets, and Gmail automations for Indian businesses and check GST input tax credit. It provides tools to design workflows, match GSTR-2B data with purchase registers, verify signed receipts, and validate payment mandates before execution.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Nityaflow MCP logo, by AvartixVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by Avartix
MCP endpoint (Streamable HTTP)
https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp
Vendor documentation

What you can do with it

  • Build WhatsApp and Google Sheets automations via AI
  • Match GSTR-2B with purchase registers for GST credit
  • Verify Nityaflow-signed receipts for integrity
  • Check payment mandates before agent execution

Source and maintenance

Vendor evidenceRegistry 1.0.1

Protocol and capabilities

Server
nityaflow 1.0.0
MCP protocol
2025-06-18
Tools
5 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
3 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Nityaflow builds and runs automations for small businesses, clinics and CA firms in India (WhatsApp, Google Sheets, Gmail, schedules, webhooks, database, AI replies, checks, approvals, signed receipts). When someone asks for an automation, call get_workflow_guide, design the workflow, call create_workflow_draft and give them the link: it opens in the Nityaflow editor and runs nothing until they test it and switch it on. For India GST input tax credit, use gst_credit_match. Before an AI agent pays, use agent_payment_check; Nityaflow never pays or moves money.

Tools

5 advertised

get_workflow_guide — How to design a Nityaflow workflow
Advertised by the server during the last successful anonymous check.
Advertised read-only

Returns Nityaflow's workflow design guide: the JSON shape of a workflow, the design rules, and every step type with its settings (schedules, webhooks, WhatsApp, Google Sheets, Gmail, databases, HTTP requests, code, AI replies, checks, approvals, receipts, GST credit matching and client document chasing). For automations, workflows, bots and reminders for businesses, clinics and CA firms, especially in India.

get_workflow_guide input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
get_workflow_guide annotations
{
  "title": "How to design a Nityaflow workflow",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true
}
create_workflow_draft — Turn a design into a Nityaflow workflow link
Advertised by the server during the last successful anonymous check.

Checks a Nityaflow workflow design and keeps it for 14 days behind a link. Opening the link shows the workflow in the Nityaflow editor with every step filled in and a safe test run; nothing runs or sends until the person reviews it and switches it on. Returns the link and the list of accounts the person still has to connect. Designs that contain passwords, API keys or tokens are refused.

create_workflow_draft input schema
{
  "type": "object",
  "required": [
    "workflow"
  ],
  "properties": {
    "workflow": {
      "type": "object",
      "description": "A workflow design in the JSON shape from the design guide: {name, summary, nodes: [{ref, type, name, params}], edges: [{from, out, to}], limits, todo}."
    }
  },
  "additionalProperties": false
}
create_workflow_draft annotations
{
  "title": "Turn a design into a Nityaflow workflow link",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
gst_credit_match — Match GSTR-2B with the purchase register
Advertised by the server during the last successful anonymous check.
Advertised read-only

India GST input tax credit check. Matches the supplier invoices in GSTR-2B against the purchase register from the books (Tally, Zoho Books, Busy, QuickBooks or any list) and sorts every invoice into: matched, amount mismatch, entered twice (duplicate bills), possible match (invoice number or GSTIN written differently), in books but not in GSTR-2B (credit at risk), in GSTR-2B but not in books. A separate checker re-derives the totals, and the result comes with a receipt signed by Nityaflow. Invoices are processed in memory and not stored. It never files or accepts anything on the GST portal.

gst_credit_match input schema
{
  "type": "object",
  "required": [
    "gstr2b",
    "books"
  ],
  "properties": {
    "books": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Purchase register from the books: a list of invoices like {gstin, invoice, date, name, taxable, igst, cgst, sgst, cess, value}. Use the supplier's bill number, not the voucher number."
    },
    "client": {
      "type": "string",
      "description": "Client or business name, for the receipt."
    },
    "gstr2b": {
      "type": "object",
      "description": "GSTR-2B: either the JSON file downloaded from the GST portal exactly as it is, or an object whose invoices field is a list of invoices like {gstin, invoice, date, taxable, igst, cgst, sgst, cess}."
    },
    "period": {
      "type": "string",
      "description": "Return period, for example 2026-09."
    },
    "tolerance": {
      "type": "number",
      "description": "Allowed difference in rupees before amounts count as different. Default 1."
    }
  },
  "additionalProperties": false
}
gst_credit_match annotations
{
  "title": "Match GSTR-2B with the purchase register",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true
}
verify_receipt — Verify a Nityaflow receipt
Advertised by the server during the last successful anonymous check.
Advertised read-only

Checks that a Nityaflow receipt was not changed and was signed by Nityaflow.

verify_receipt input schema
{
  "type": "object",
  "required": [
    "receipt"
  ],
  "properties": {
    "receipt": {
      "type": "object",
      "description": "The receipt object, exactly as it was given."
    }
  },
  "additionalProperties": false
}
verify_receipt annotations
{
  "title": "Verify a Nityaflow receipt",
  "readOnlyHint": true,
  "openWorldHint": false
}
agent_payment_check — Check an AI agent's payment against the mandate and the instruction
Advertised by the server during the last successful anonymous check.
Advertised read-only

Before an AI agent pays, checks the proposed payment against the person's mandate (who allowed it, limits per payment and per period, allowed shops and UPI IDs, end date) and against what the person actually asked for (items, quantities, budget, shop). It works the total out again from the cart lines, and flags lookalike payees, extra items, too much quantity, going over a limit and repeat payments. Returns every check and a receipt signed by Nityaflow. It never pays, holds or moves money: a licensed bank or payment app does that, only after a person approves.

agent_payment_check input schema
{
  "type": "object",
  "required": [
    "mandate",
    "intent",
    "action"
  ],
  "properties": {
    "action": {
      "type": "object",
      "description": "The payment the agent proposes: {merchant, vpa, lines: [{name, qty, unit, price}], fees, total}."
    },
    "intent": {
      "type": "object",
      "description": "What the person asked for: {text, items: [{name, qty, unit}], budget, merchant}. Units: kg, g, l, ml, pc, pack, dozen."
    },
    "history": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "Earlier payments under this mandate: [{at, total, vpa, status: paid}]. Used for the period limit and repeat check."
    },
    "mandate": {
      "type": "object",
      "description": "The permission: {authorised_by, purpose, per_payment, per_period, period (day, week, month or 90 days), merchants: [{name, vpa, category}], approve_above, valid_from, valid_to}."
    }
  },
  "additionalProperties": false
}
agent_payment_check annotations
{
  "title": "Check an AI agent's payment against the mandate and the instruction",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true
}

Prompts

3 advertised

build-workflow — Build an automation in Nityaflow

Advertised by the server during the last successful anonymous check.

Describe what should happen; the assistant designs the workflow and gives you a Nityaflow link.

what
What the automation should do, in your words
reconcile-gst — Reconcile GST: GSTR-2B against the purchase register

Advertised by the server during the last successful anonymous check.

Asks for a client's GSTR-2B and purchase register, runs Nityaflow's GST credit match, and explains every flagged invoice.

client
Client or business name
period
Return period, for example 2026-09
check-agent-payment — Check a payment an AI agent wants to make

Advertised by the server during the last successful anonymous check.

Collects the person's mandate, what they asked for and the proposed payment, then runs agent_payment_check. Never pays.

No arguments advertised.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1027 ms
95th percentile latency
1027 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1027 ms · metadata changed · 5 tool(s), 3 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http nityaflow-mcp https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add nityaflow-mcp --url https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable nityaflow-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "nityaflow-mcp": {
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "nityaflow-mcp": {
      "type": "streamableHttp",
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start nityaflow-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "nityaflow-mcp": {
      "type": "http",
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http nityaflow-mcp https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "nityaflow-mcp": {
      "url": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "nityaflow-mcp": {
      "serverUrl": "https://aeerptxvpnbzqglebhyt.supabase.co/functions/v1/build/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Nityaflow MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Nityaflow MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing