Usage Example

How to use the BlueNexus Universal MCP Server

To integrate the BlueNexus Universal MCP Server into your existing architecture, you can use the following configuration and implementation guidelines.

The MCP server supports Dynamic Client Registration and uses Bearer Tokens.

1. MCP Client Configuration

Add the BlueNexus endpoint to your environment configuration. Your system will use the Bearer token (Personal Access Token) to authenticate the initial registration and subsequent tool-calling requests.

{
  "mcpServers": {
    "bluenexus": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/sdk"],
      "env": {
        "BLUENEXUS_API_URL": "https://api.bluenexus.ai/mcp",
        "AUTH_TYPE": "Bearer",
        "BEARER_TOKEN": "YOUR_BLUENEXUS_PERSONAL_ACCESS_TOKEN"
      }
    }
  }
}

2. Integration Workflow

1. Handshake: Your client initiates a connection to https://api.bluenexus.ai/mcp using your Bearer token.

2. Capability Discovery: Instead of the server sending hundreds of individual tools, BlueNexus will register as a Consolidated Context Tool.

3. Dynamic Scoping: If your client supports dynamic registration, it can negotiate specific scopes (e.g., calendar.read, drive.file) during the initial session setup, which BlueNexus maps to your existing OAuth connections.

3. Implementation Example (Node.js/TypeScript)

If you are programmatically connecting a custom agent, you can use the following logic to inject the Bearer token into the transport layer:

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { SSEClientTransport } from "@modelcontextprotocol/sdk/client/sse.js";

const transport = new SSEClientTransport(
  new URL("https://api.bluenexus.ai/mcp"),
  {
    eventSourceInit: {
      headers: {
        // Your existing Bearer token authentication
        'Authorization': `Bearer ${process.env.BLUENEXUS_TOKEN}`,
        'Content-Type': 'application/json'
      }
    }
  }
);

const client = new Client({
  name: "Internal-Agent-Alpha",
  version: "1.0.0"
});

await client.connect(transport);

// The Context Engine now handles the tool-routing automatically
const result = await client.callTool({
  name: "get_unified_context",
  arguments: {
    query: "Summarize Q4 budget discussions from Slack and Notion"
  }
});

4. Key Technical Requirements

• Transport Layer: Ensure your client supports SSE (Server-Sent Events), as BlueNexus uses this for real-time context streaming.

• Header Propagation: Your dynamic registration module must be configured to pass the Authorization header in all lifecycle events (initialize, ping, resources/list).

• Token Rotation: Ensure your Bearer token management service refreshes the BlueNexus token before expiration to prevent context retrieval failures mid-conversation.