AI tools & MCP server
Point your AI tool at the Setu docs and it searches and reads them itself, instead of answering from memory or waiting for you to paste pages in.
MCP server
Add this one URL to your AI tool. There is no key and no sign-in, and the server is read-only.
https://docs.setu.co/api/mcpConnect your tool
Pick your tool and follow its steps. Menu names in the app tabs are as of September 2026.
Run once; --scope user makes it available in every project, including the desktop app's Code tab:
claude mcp add --transport http --scope user setu-docs https://docs.setu.co/api/mcpStart a new session, then ask your question as usual; the agent calls search and get_page on
these docs and answers from the pages it read. /mcp inside a session lists the server and its tools.
Try it
Start a new chat or session and ask a real question, for example:
- "Using the Setu docs, how do I verify a customer's bank account with reverse penny drop?"
- "Which UPI apps can a UPI DeepLinks payment link open?"
- "Show me how to start an Account Aggregator consent flow in TypeScript."
Your tool searches the docs and reads the matching page before it answers. If it answers without searching, ask it to use the Setu docs.
What your tool can do
| Tool | What it does |
|---|---|
search | Searches every page. Returns up to ten matching pages, each with the passages that matched and its path. Short keyword queries work better than full sentences. |
get_page | Returns one page as Markdown, by its path, for example /payments/bbps/overview. |
list_pages | Lists the documentation pages with their titles and descriptions. Redirects and empty landing pages are left out, so every path it returns works with get_page. |
This server answers questions about the documentation. It is not the BillPay MCP server, which lets an assistant fetch and pay bills on a customer's behalf and needs OAuth. For that, see the BillPay MCP integration guide.
Requests are rate limited per IP address (60 per minute), which is plenty for interactive use.
Markdown for any page
Add .mdx to the end of any documentation page URL to get it as plain Markdown. For example,
/payments/bbps/overview.mdx is the BBPS overview. Every documentation
page also has a Copy Markdown button next to its title.
llms.txt
/llms.txtlists every page with its title, description and link, in the llmstxt.org format./llms-full.txtis the full text of every page in one file (about 2 MB).