
Inflow
ai.inflowpay.appPublished by app.inflowpay.aiOfficial publisherv1.0.3Updated Oct 24, 2026
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Overview
Connects an AI assistant to an InFlow payment and wallet account so it can check balances, review transactions, and manage policies and approvals.
- What you can do
- InFlow exposes tools for balances, transactions, deposits, withdrawals, policies, approvals, and account details over Streamable HTTP. An assistant can look up balances across currencies and wallets, view transaction history, list deposit addresses, create withdrawal addresses, and initiate withdrawals. It can also create and update transaction policies and review, approve, or decline pending approval requests. Available tools depend on the account role.
- When to use it
- Useful if you already hold an InFlow account and want to manage payments and wallet activity conversationally instead of navigating the dashboard. Suited to developers, merchants, or individuals who want balance checks, transaction review, and approval handling inside an MCP client.
- Requirements
- A remote MCP endpoint at using Streamable HTTP; no local package is needed. An InFlow account and an MCP-compatible client are required. Authorization uses OAuth 2.1 with PKCE, so you log in and grant access through the browser; the client then manages the session.
Installation
In SourceWeft
- Open Inflow in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.inflowpay.app%2Finflow/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"inflow": {
"type": "http",
"url": "https://app.inflowpay.ai/mcp"
}
}
}README
[MCP Compatible] [OAuth 2.1] [License: MIT] [Streamable HTTP]
InFlow MCP Server
Connect your AI assistant to InFlow for managing payments, wallets, and transactions via the Model Context Protocol.
Quick Start
Server URL:
MCP Configuration:
What is MCP?
The Model Context Protocol (MCP) is an open standard that allows AI assistants — like Claude, ChatGPT, Cursor, and others — to connect directly to external services. Instead of copying and pasting information between your AI assistant and InFlow, MCP lets your assistant interact with InFlow on your behalf: checking balances, approving payments, managing policies, and more — all through natural conversation.
Think of it like giving your AI assistant a secure, authorized connection to your InFlow account.
What is InFlow?
InFlow is a payment and wallet platform that allows you to review and manage digital transactions. Whether you are a developer integrating payments into your application, a merchant accepting payments, or an individual managing a wallet, InFlow provides the tools to do so. Connecting your AI assistant to InFlow via MCP means you can manage your account conversationally, without needing to navigate the dashboard for every action.
What Can You Do with the InFlow MCP?
Once connected, your AI assistant can help you with a range of tasks, including:
- Balances — Check your current balances across currencies and wallets.
- Transactions — View transaction history and check transaction details.
- Deposit & Withdrawal — View deposit addresses, create withdrawal addresses, and initiate withdrawals.
- Policies — Create, update, and manage transaction policies that govern how your account operates.
- Approvals — Review, approve, or decline pending approval requests.
- Account — View your account details and profile information.
You interact with these capabilities using natural language. For example, you might ask your assistant:
- "What is my current balance?"
- "Do I have any pending approvals?"
- "Show me my transactions from the last week"
- "Create a policy that requires approval for transactions over $500"
Prerequisites
- An InFlow account. If you do not have one, you can register at app.inflowpay.ai.
- An AI assistant or MCP client that supports the Model Context Protocol (such as Claude, Cursor, VS Code, or any MCP-compatible client).
Setup
There are two ways to connect your AI assistant to InFlow: through your client's built-in marketplace, or by manually adding the connection.
Option 1: Find InFlow in Your Client's Marketplace
Many MCP clients have a built-in marketplace or connector directory where you can search for available services. To connect this way:
- Open your AI assistant's settings or connector marketplace.
- Search for "InFlow".
- Select InFlow from the results and follow the prompts to authorize your account.
- You will be redirected to InFlow to log in and grant access. Once authorized, the connection is complete.
Option 2: Add InFlow Manually
If your client does not list InFlow in its marketplace, or if you prefer to set up the connection manually, you can add it using the MCP server URL:
The general steps are:
- Open your MCP client's settings for adding a new connector or MCP server.
- Use InFlow as the name or title for the connection.
- Enter
https://app.inflowpay.ai/mcpas the MCP server URL (sometimes called the server URL or endpoint). - Save the connection. Your client will redirect you to InFlow to log in and authorize access.
Below are step-by-step instructions for popular clients.
Claude
- Open Settings → Connectors → Add custom connector.
- Enter
https://app.inflowpay.ai/mcpas the URL. - Complete the OAuth authorization when prompted.
Cursor
Create or edit your MCP configuration file at ~/.cursor/mcp.json (global) or .cursor/mcp.json (project) and add:
Then enable the server in Cursor settings if prompted.
Visual Studio Code
Open the Command Palette → MCP: Add Server → select HTTP and use:
Claude Code (CLI)
Run the following command in your terminal:
Other Clients
For any other MCP-compatible client, you can use npx to connect:
Or use the server URL directly if your client supports Streamable HTTP transport:
Authentication
After adding the InFlow connector, your MCP client will redirect you to InFlow to log in and authorize the connection. This uses OAuth 2.1 with PKCE, the same industry-standard protocol used by services like Google and GitHub for secure authorization. You will only need to authorize once; your client will manage the session from there.
The tools available to your assistant depend on your InFlow account role. For example, a developer account may see different capabilities than a merchant account. You will only see tools that your account is authorized to use.
Troubleshooting
I cannot find InFlow in my client's marketplace. Not all clients have InFlow listed yet. Use the manual setup instructions above to add the connection directly.
The OAuth authorization is not completing.
Make sure you are logged in to your InFlow account in your browser. If you are still having trouble, try clearing your browser cookies for app.inflowpay.ai and trying again.
My assistant says it cannot access a certain tool. Tool availability is based on your account role. If you believe you should have access to a tool that is not appearing, contact support at [email protected].
Support
If you run into any issues or have questions about the InFlow MCP, reach out to us at [email protected].
Source: README.md at commit 6fd5750
Tools
0Version history
1- v1.0.3LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts