← Registry

Marketing

oxeflow.com.br

This MCP server integrates with OxeFlow to schedule operational diagnostic calls, capture leads, and present case studies for marketing and sales purposes.

1 endpoint9 known toolsFirst detected August 13, 2026Last detected August 13, 2026

ENDPOINT 1

https://mcp.oxeflow.com.br/mcp

No auth detected

MCP server metadata

Name
MCP_Server_Trigger
Version
0.1.0
Capabilities
tools

Known tools 9

cancelar_diagnostico

Cancel a booked operational diagnostic.

Inferred read-only
agendar_diagnostico

Book a 30-minute operational diagnostic video call with OxeFlow on a slot returned by listar_horarios_disponiveis.

Inferred read-only
listar_horarios_disponiveis

List available 30-minute slots for a FREE operational diagnostic video call with OxeFlow (Google Meet).

Inferred read-only
captar_lead

Register a business lead with OxeFlow.

Inferred read-only
detalhar_case

Full OxeFlow case study detail as Markdown.

Inferred read-only
listar_cases

List OxeFlow real-world case studies (index page): AI-driven customer service automation at a diagnostic clinic (Via Médica) and an international legal operation (StudioKF).

Inferred read-only
engenharia_oxeflow

OxeFlow engineering: the architecture and stack behind the operations OxeFlow runs — n8n orchestration, omnichannel platform (OxeChat), WhatsApp Business Platform, PostgreSQL/Redis, own Docker infrastructure.

Inferred read-only
solucoes_oxeflow

OxeFlow solutions and services: AI agents for business, business process automation, WhatsApp automation, system integration and operational intelligence — designed, deployed and operated by OxeFlow.

Inferred read-only
sobre_oxeflow

About OxeFlow: company profile, positioning, what we do (AI agents, business process automation, system integration, operational intelligence) and official Meta Tech Provider status.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mcp_server_trigger]
url = "https://mcp.oxeflow.com.br/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "mcp_server_trigger": {
      "type": "http",
      "url": "https://mcp.oxeflow.com.br/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: mcp_server_trigger
Remote MCP URL: https://mcp.oxeflow.com.br/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mcp_server_trigger": {
      "url": "https://mcp.oxeflow.com.br/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "mcp_server_trigger": {
      "type": "http",
      "url": "https://mcp.oxeflow.com.br/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "mcp_server_trigger",
  "transport": "streamable-http",
  "url": "https://mcp.oxeflow.com.br/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.