Hosted MCP server/Finance

MerchantFlow MCP server

Provider setup path

MerchantFlow provides unified ecommerce profitability analytics for AI agents. The endpoint at https://merchantflow.ai/api/mcp responded with an authentication challenge when checked, so the service exists, but the documentation site does not publish transport or OAuth details. The previous malformed checkout-champ URL has been replaced with the docs home.

OAuth (endpoint responds with auth challenge) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Ecommerce teams that need unified profitability analytics and can confirm connection details with the provider.

  • Ask the provider for the MCP transport and OAuth setup.
  • Connect to the profitability analytics endpoint.
  • Review ecommerce profitability by channel.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Provider endpoint (documentation pending)

The provider endpoint answered an auth challenge when checked, but the docs site does not publish an MCP page. Confirm transport and OAuth details with MerchantFlow before connecting.

https://merchantflow.ai/api/mcp

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

MerchantFlow documentationhttps://docs.merchantflow.ai/