Inflowave MCP server: official

How to connect Inflowave MCP to Claude Desktop

Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.

{
  "mcpServers": {
    "inflowave": {
      "command": "npx",
      "args": ["mcp-remote", "<YOUR_MCP_URL>"]
    }
  }
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.inflowave.io
// Claude Code (one-liner): claude mcp add inflowave <YOUR_MCP_URL> --transport http

Some MCP servers require an API key. Check the source page for setup: mcp.inflowave.io.

Does Inflowave MCP cost extra?

Included with subscription

Inflowave ships an official MCP server that uses your existing subscription credentials.

No separate MCP licence to buy. You pay for your Inflowave plan, the MCP server queries that account.
Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.

Inflowave also publishes a REST API

Inflowave publishes an API, but per-tier gating wasn't extracted automatically.

API docs

—

Auth method

—

SDK languages

—

OpenAPI spec

—

Webhooks

—

Structured outputs

—

See Inflowave API page

What you can do with Inflowave from an AI agent

Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.

INDIE / SOLO

Skip the dashboard, ask Claude

"What deals stalled this week?" answered in seconds
Quick one-off questions without leaving the editor
Pipe Inflowave data into your personal notes / docs without writing a script

Effort: 30 seconds — paste the config, restart Claude

AGENCY

Run client analysis at agent speed

Hand the MCP server to your team — every consultant can ask Claude about any client's Inflowave account
Multi-account workflows without context-switching the Inflowave UI
Reports you'd normally spend hours on, done before standup

Effort: An afternoon — set up auth per client

IN-HOUSE TEAM

Production agent workflows

Embed in your internal Codex / Cursor agents that triage Inflowave data daily
Combine with other MCP servers in a multi-step agent chain
Constrain agents to read-only roles to keep production Inflowave safe

Effort: Days — security review + role config

Limits and gotchas

Official MCP server — published by Inflowave themselves, so it should track product changes.
Fallback: the REST API works for any flow the MCP server doesn't cover.
Rate limits: MCP calls count against your underlying Inflowave API quota. Burst usage from a curious agent can drain a daily allowance fast.

Inflowave MCP & API FAQ

Is the Inflowave MCP server official?

Yes — an official, vendor-maintained server at https://mcp.inflowave.io.

Can I use the Inflowave MCP with Cursor or Codex?

Yes — MCP is a protocol, not Claude-specific. Any MCP-capable client (Cursor, Codex, Windsurf, Zed) can use the same server config with minor path adjustments.

Sources

Inflowave official site: https://inflowave.io
MCP server page: https://mcp.inflowave.io

Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

Joonas RotkoAuthor & Founder of That Marketing Buddy

10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.

About me How I review

Inflowave MCP Server

What is the Inflowave MCP server?

What you can build with the Inflowave MCP