Flowie Exchange: send e-invoices in 150 countries

com.get-flowiePublished by get-flowie.comv1.3.0Updated Nov 7, 2026

One API to send and receive compliant e-invoices in 150 countries via Sovos, from any ERP.

The publisher's own server: Exchange.news — Crypto offers, campaigns and news

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant send and receive compliant e-invoices in 150 countries via Sovos, from any ERP.

What you can do
  • Send compliant e-invoices in 150 countries through the Sovos network
  • Receive incoming e-invoices and route them into an ERP workflow
  • Act as a single API layer between an assistant and country-specific e-invoicing requirements
When to use it
Useful when an assistant should help issue or collect legally compliant e-invoices across multiple countries, or when you want e-invoicing handled from an existing ERP without building per-country integrations.
Requirements
A remote MCP endpoint at back.p2p-flowie.com over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
The server sends real invoices to tax and business partners, so actions are outward-facing and hard to undo. OAuth grants access to your Flowie account; review the scopes before connecting. Invoice data is passed to Sovos as a third party. No tool list is published, so confirm exactly what it can send or change before use.

Installation

In SourceWeft

  1. Open Flowie Exchange: send e-invoices in 150 countries in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.get-flowie%2Fexchange/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "flowie-exchange-send-e-invoices-in-150-c": {
      "type": "http",
      "url": "https://back.p2p-flowie.com/exchange/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.3.0LatestNov 7, 2026
  2. v1.1.0Nov 6, 2026
  3. v1.0.0Oct 20, 2026

Score

83% 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
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Exchange integrations