GST refund software with an MCP connection: what to check
Understand what an MCP connection should expose for GST refund work, how it differs from an API, and what Fast GST Refund currently offers to AI assistants.
Fast GST Refund does not currently publish an MCP server. Today, it exposes only a small read-only OpenAPI endpoint for public guidance. The self-serve refund automation product and any agent connection are still being built.
No public MCP endpoint for MyGSTRefund or Gen GST was identified in the official product material reviewed for this guide. Do not grant an unofficial connector access to GST credentials or taxpayer files merely because it uses a familiar product name.
MCP versus a normal API
The Model Context Protocol lets a server expose tools, resources and prompts to an AI application. Tools are callable operations; resources supply contextual data. MCP server overview.
An OpenAPI document describes HTTP operations. An agent platform may be able to turn that API into a tool, but this does not make the endpoint an MCP server. Check the actual transport, authentication and published capabilities.
| Connection | What it tells an assistant | What it does not prove |
|---|---|---|
Web page or llms.txt |
Where public guidance can be read | Structured calls, authentication or safe actions |
| OpenAPI | HTTP paths, inputs and response shapes | MCP compatibility or permission handling |
| MCP server | Discoverable tools/resources through the protocol | That the tax logic or data controls are correct |
| GSTN/accounting API | Programmatic access to a source system | That the integration may file or assess a refund lawfully |
What Fast GST Refund exposes today
The public operation is:
GET https://fastgstrefund.com/api/checklist?stage=preparing&need=statement3It requires no account or email and returns public preparation guidance. It cannot read files, inspect a GST account, calculate refund entitlement, validate documents or file an application. See the agent usage guide and OpenAPI specification.
This endpoint is the public validation layer, not the refund automation product. It lets an assistant surface guidance without receiving sensitive taxpayer data.
Where agents fit in the Fast GST Refund workflow
Fast GST Refund is designed around a controlled automation workspace: import source records, reconcile invoices and receipts, surface exceptions, compute a traceable working, and prepare validated Statement 3 and Annexure B outputs.
An MCP connection could eventually let an assistant inspect claim status, explain an exception or request a specific review step. We are also exploring isolated workspaces that can operate Excel, official offline utilities and other desktop tools used during preparation. Those capabilities are still in development; no public MCP server, desktop harness or filing tool is available today.
What a useful refund MCP server would need
A production connector should expose small, auditable tools rather than one powerful “do my refund” action.
| Possible tool | Minimum safe behaviour |
|---|---|
list_claim_sources |
Return metadata, not document contents, until the user selects a claim |
reconcile_export_receipts |
Show invoice, receipt and unmatched balances with source references |
review_itc_exceptions |
Surface 2B mismatches, reversals, RCM and classification questions without deciding silently |
compute_refund_draft |
Return formula inputs, caps and warnings; label the result a draft |
validate_statement_files |
Report schema errors without changing source transactions |
prepare_filing_preview |
Produce a reviewable preview; never sign or submit by default |
submit_rfd01 |
Require explicit user confirmation, authorised identity and a complete audit record |
The current MCP SDK guidance distinguishes tools from resources and supports structured tool descriptions. A tax connector should also describe which actions are read-only, mutating or externally consequential so the host can request appropriate confirmation. MCP TypeScript SDK overview.
Security questions before connecting
Ask the provider:
- Is the server operated by the named software vendor or an independent third party?
- What exact tools and resources become available after authorisation?
- Which calls read GSTN, accounting, bank or document data?
- Can any tool alter books, push data, file a return or submit RFD-01?
- Is each consequential action separately confirmed and logged?
- How are GSTINs, tokens, files, prompts and outputs retained or used?
- Can access be limited per client, period and user, then revoked immediately?
Treat prompt injection inside invoices, emails and uploaded documents as untrusted input. A connected assistant should not follow document text that asks it to reveal secrets, bypass review or invoke another tool.
Should you wait for MCP?
No, if your current problem is incomplete records or an unexplained mismatch. Start with stable file exports and a clear review pack. Use how to export Zoho Books data and the CA software buying checklist.
MCP becomes valuable when the underlying process is already controlled and you want an assistant to retrieve evidence, surface exceptions or draft a review. It should shorten navigation—not remove taxpayer consent, professional judgement or final filing review.