Server data from the Official MCP Registry
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Remote endpoints: streamable-http: https://app.inflowpay.ai/mcp
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
Endpoint verified · Requires authentication · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"ai-inflowpay-app-inflow": {
"url": "https://app.inflowpay.ai/mcp"
}
}
}From the project's GitHub README.
Connect your AI assistant to InFlow for managing payments, wallets, and transactions via the Model Context Protocol.
Server URL:
https://app.inflowpay.ai/mcp
MCP Configuration:
{
"mcpServers": {
"inflow": {
"type": "http",
"url": "https://app.inflowpay.ai/mcp"
}
}
}
| Feature | Details |
|---|---|
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 (PKCE) |
| Tools | Balances, Transactions, Deposits, Withdrawals, Policies, Approvals, Account |
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.
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.
Once connected, your AI assistant can help you with a range of tasks, including:
You interact with these capabilities using natural language. For example, you might ask your assistant:
There are two ways to connect your AI assistant to InFlow: through your client's built-in marketplace, or by manually adding the connection.
Many MCP clients have a built-in marketplace or connector directory where you can search for available services. To connect this way:
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:
https://app.inflowpay.ai/mcp
The general steps are:
https://app.inflowpay.ai/mcp as the MCP server URL (sometimes called the server URL or endpoint).Below are step-by-step instructions for popular clients.
https://app.inflowpay.ai/mcp as the URL.Create or edit your MCP configuration file at ~/.cursor/mcp.json (global) or .cursor/mcp.json (project) and add:
{
"mcpServers": {
"inflow": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.inflowpay.ai/mcp"]
}
}
}
Then enable the server in Cursor settings if prompted.
Open the Command Palette → MCP: Add Server → select HTTP and use:
{
"servers": {
"inflow": {
"type": "http",
"url": "https://app.inflowpay.ai/mcp"
}
}
}
Run the following command in your terminal:
claude mcp add --transport http inflow https://app.inflowpay.ai/mcp
For any other MCP-compatible client, you can use npx to connect:
npx -y mcp-remote https://app.inflowpay.ai/mcp
Or use the server URL directly if your client supports Streamable HTTP transport:
https://app.inflowpay.ai/mcp
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.
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 support@inflowpay.ai.
If you run into any issues or have questions about the InFlow MCP, reach out to us at support@inflowpay.ai.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.