Nexus MCP Client

Nexus MCP Client is a proxy that connects Claude Desktop to the Nexus MCP Server via HTTP/SSE, enabling seamless access to enterprise-grade MCP orchestration capabilities.

🚀 Quick Start

Installation & Usage

No installation required! Use directly with npx:

npx nexus-mcp-client --client-id your-client-id

Claude Desktop Configuration

Add this to your Claude Desktop MCP configuration file:

{
  "mcpServers": {
    "nexus-orchestrator": {
      "command": "npx",
      "args": [
        "-y",
        "nexus-mcp-client",
        "--server",
        "https://alten.nexus-mcp.es",
        "--client-id",
        "YOUR_CLIENT_ID"
      ],
      "env": {
        "NODE_ENV": "production"
      }
    }
  }
}

Replace YOUR_CLIENT_ID with your unique client identifier.

📋 Available Options

npx nexus-mcp-client [options]

Options:
  -s, --server <url>       Nexus server URL (default: https://alten.nexus-mcp.es)
  -c, --client-id <id>     Client ID for identification (required)
  -t, --timeout <ms>       Connection timeout in milliseconds (default: 30000)
  -r, --retries <count>    Number of retry attempts (default: 3)
  --debug                  Enable debug logging
  -V, --version            Display version number
  -h, --help              Display help information

🛠️ Usage Examples

Basic Usage

npx nexus-mcp-client --client-id my-company-dev-001

Custom Server

npx nexus-mcp-client \\
  --server https://nexus.mycompany.com \\
  --client-id enterprise-team-alpha

With Debug Logging

npx nexus-mcp-client \\
  --client-id debugging-session \\
  --debug

Full Configuration

npx nexus-mcp-client \\
  --server https://nexus.enterprise.com \\
  --client-id enterprise-client-456 \\
  --timeout 60000 \\
  --retries 5

🔧 How It Works

The Nexus MCP Client acts as a transparent proxy between Claude Desktop and the Nexus MCP Server:

1. Client Connection: Connects to Nexus server via HTTP/SSE using your client ID
2. Tool Discovery: Fetches available MCP tools from the server
3. Request Proxying: Forwards Claude Desktop requests to the Nexus server
4. Response Handling: Returns server responses back to Claude Desktop

Claude Desktop ←→ nexus-mcp-client ←→ Nexus MCP Server
                       (proxy)              (cloud)

🏢 Enterprise Features

Client Identification

• Each client is uniquely identified by client-id
• Enables user tracking, analytics, and billing
• Supports multi-tenant enterprise deployments

Real-time Communication

• Server-Sent Events (SSE) for real-time updates
• Automatic reconnection and error handling
• Efficient HTTP-based tool execution

Security & Reliability

• Secure HTTPS communication
• Automatic retry logic with exponential backoff
• Graceful error handling and reporting

🌐 Supported Servers

Default Server

• URL: https://alten.nexus-mcp.es
• Status: Production-ready
• Features: Full Nexus MCP orchestration capabilities

Custom Servers

The client supports any Nexus MCP Server deployment. Contact your system administrator for your organization's server URL.

📊 Available MCP Tools

When connected to a Nexus server, you'll have access to:

• execute_tool - Universal proxy to any MCP service
• get_context_state - Retrieve project context and progress
• update_progress - Create checkpoints and recovery instructions
• create_execution_plan - Generate detailed execution plans
• generate_smart_execution_plan - AI-enhanced planning with insights
• get_role_instructions - Role-specific workflows and best practices

🔍 Troubleshooting

Connection Issues

# Test connection to server
curl https://alten.nexus-mcp.es/health

# Check with debug logging
npx nexus-mcp-client --client-id test --debug

Common Problems

Error: --client-id is required

• Solution: Always provide a unique client ID

Error: Failed to connect to Nexus server

• Check your internet connection
• Verify the server URL is correct
• Try with --debug flag for more details

Error: Tool execution failed

• Your client ID might not be authorized
• Check server status at the health endpoint

Debug Logs

Enable detailed logging with the --debug flag:

npx nexus-mcp-client --client-id my-client --debug

🔐 Security Considerations

• Client ID: Acts as your identity - keep it secure
• HTTPS: All communication is encrypted
• No Local Storage: No sensitive data stored locally
• Server Trust: Only connect to trusted Nexus servers

📚 API Reference

NexusMCPClient Class

import { NexusMCPClient } from 'nexus-mcp-client';

const client = new NexusMCPClient({
  serverUrl: 'https://your-nexus-server.com',
  clientId: 'your-client-id',
  timeout: 30000,  // optional
  retries: 3       // optional
});

await client.start();

Configuration Interface

interface NexusClientConfig {
  serverUrl: string;    // Nexus server URL
  clientId: string;     // Unique client identifier
  timeout?: number;     // Connection timeout (default: 30000)
  retries?: number;     // Retry attempts (default: 3)
}

🤝 Support

Community Support

• GitHub Issues: Report bugs or request features
• Discord: Join our developer community

Enterprise Support

• Email: [email protected]
• Documentation: Enterprise guides

📄 License

MIT License - see LICENSE file for details.

🔗 Related Projects

• Nexus MCP Server - The core orchestration server
• Claude Desktop - AI assistant with MCP support
• Model Context Protocol - The underlying protocol

Made with ❤️ by the Nexus Team

Simplifying AI workflows, one connection at a time.