Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://app.inflowpay.ai/mcpRun this in your terminal
claude mcp add --transport http inflow https://app.inflowpay.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"inflow": {
"url": "https://app.inflowpay.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"inflow": {
"type": "http",
"url": "https://app.inflowpay.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://app.inflowpay.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain app.inflowpay.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.