inbrix

ai.inbrixPublished by inbrix.aiOfficial publisherv1.0.0Updated Oct 30, 2026

AI-native helpdesk hosted in Germany: tickets, replies, KPIs and knowledge base over MCP.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Inbrix is a Germany-hosted, AI-native helpdesk that exposes tickets, replies, KPIs and a knowledge base to an assistant over MCP.

What you can do
  • Work with support tickets: read and manage helpdesk tickets.
  • Draft and send replies to customer conversations.
  • Review KPIs and support performance metrics.
  • Look up and use knowledge base content for answers.
When to use it
Useful when a support or service team already runs its helpdesk on Inbrix and wants an assistant to triage tickets, draft replies, pull KPIs or consult the knowledge base without leaving the chat.
Requirements
A remote MCP endpoint at app.inbrix.ai reached over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared; an Inbrix account with access to the helpdesk is implied.
Before you install
The assistant can act on live customer conversations, so replies and ticket changes may be visible to customers or colleagues. Access is granted through OAuth to the connected Inbrix account, and helpdesk data is held by a third-party provider in Germany.

Installation

In SourceWeft

  1. Open inbrix 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/ai.inbrix%2Fhelpdesk/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": {
    "inbrix": {
      "type": "http",
      "url": "https://app.inbrix.ai/api/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

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.