BNex

com.ziyncPublished by ziync.comOfficial publisherv1.0.0Updated Oct 24, 2026

BNex lets AI securely access your workspace data like contacts and campaigns via MCP.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

BNex gives an AI assistant secure access to workspace data such as contacts and campaigns through a hosted MCP endpoint.

What you can do
BNex is a remote MCP server that connects an assistant to a workspace's business data. According to its description, it provides secure access to data such as contacts and campaigns. No individual tools are listed in the supplied material, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs to work with contacts, campaigns, or similar workspace records held in BNex, and you want that access brokered through MCP rather than manual exports.
Requirements
A remote MCP connection to the hosted endpoint at bnex.ziync.com over streamable HTTP. OAuth authentication is required, so a BNex account with the appropriate workspace access is needed. No environment variables or headers are declared.
Before you install
Access is to workspace business data, including contacts and campaigns, so review what the OAuth grant exposes before connecting. The supplied material does not document which tools can read, write, send, or delete data, so confirm those permissions in the provider's documentation first.

Installation

In SourceWeft

  1. Open BNex 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.ziync%2Fbnex/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": {
    "bnex": {
      "type": "http",
      "url": "https://bnex.ziync.com/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.0LatestOct 12, 2026

Score

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

    Publish an icon in the registry entry.

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