Genudo MCP Client

A lightweight bridge that connects Claude Code to Genudo's Model Context Protocol (MCP) server, enabling AI-powered workflow automation directly from your Claude Code interface.

Overview

Genudo MCP Client bridges the communication gap between Claude Code's stdio-based MCP implementation and Genudo's HTTP/SSE-based MCP server. This allows you to leverage Genudo's powerful business automation tools directly within your Claude Code conversations.

Features

Access Genudo's business automation tools directly from Claude Code. The server exposes 21 tools across five areas:

• 📊 Analytics — account summary, messaging volume stats, AI performance & cost (get_account_summary, get_messaging_stats, get_ai_performance)
• 🔎 Read your workspace — list pipelines, stages, contacts, messages, opportunities, and variables (list_pipelines, list_pipeline_stages, list_contacts, list_messages, list_opportunities, list_variables)
• 🚀 Build pipelines — a guided step-by-step builder plus direct create/update (start_pipeline_journey, get_pipeline_options, create_pipeline, update_pipeline)
• 🧩 Stages & actions — configure pipeline stages and external-integration actions/webhooks (create_stage, update_stage, create_action, update_action)
• ⚙️ Variables & opportunities — manage pipeline variables and update opportunities (create_variable, update_variable, delete_variable, update_opportunities)

Three workflows to start with

1. Audit my AI business operations — Claude pulls your account, messaging, and AI-cost stats and surfaces the top fixes.
2. Analyze my agent performance — spot expensive agents, low-completion stages, and actions that aren't triggering.
3. Create or improve a pipeline — e.g. "Create a Messenger sales agent for a summer camp; collect name, phone, branch, child age; escalate on special-needs questions."

Quick Start

One command — no clone, no manual config:

claude mcp add --env GENUDO_API_KEY=YOUR_KEY --transport stdio genudo -- npx -y genudo-mcp-client

Replace YOUR_KEY with your Genudo API key (Settings → API Keys). Restart Claude Code and start using Genudo tools!

Prerequisites

• Node.js 18.0.0 or higher
• A Genudo account with API access
• Your Genudo API key

Installation

Recommended: one command

claude mcp add --env GENUDO_API_KEY=YOUR_KEY --transport stdio genudo -- npx -y genudo-mcp-client

npx fetches and runs the published package — no clone, no local path. Get your API key from Settings → API Keys, then restart Claude Code.

Alternative: from source

For local development or contributions:

git clone https://github.com/genudo-ai/genudo_mcp.git
cd genudo_mcp
npm install

Then configure Claude Code manually (see Configuration section below).

Configuration

Step 1: Get Your API Key

1. Log in to your Genudo account
2. Navigate to Settings → API Keys
3. Click Generate New API Key
4. Copy your API key (keep it secure!)

Step 2: Connect your MCP client

Recommended — Claude Code, one command:

claude mcp add --env GENUDO_API_KEY=YOUR_KEY --transport stdio genudo -- npx -y genudo-mcp-client

Other clients (Codex, Cursor, Windsurf, Claude Desktop): same package, add this block to the client's MCP config:

{
  "mcpServers": {
    "genudo": {
      "command": "npx",
      "args": ["-y", "genudo-mcp-client"],
      "env": {
        "GENUDO_API_KEY": "your_api_key_here"
      }
    }
  }
}

If you cloned the repo rather than using the published package, point at your local index.js:

{
  "mcpServers": {
    "genudo": {
      "command": "node",
      "args": ["/absolute/path/to/genudo_mcp/index.js"],
      "env": { "GENUDO_API_KEY": "your_api_key_here" }
    }
  }
}

Replace the path with where you cloned the repo.

Step 3: Restart Claude Code

Exit your current Claude Code session and start a new one:

# Exit current session
exit

# Start new session
claude

Usage

Once configured, Claude Code will automatically have access to your Genudo tools. You can use them in your conversations:

Example:

User: "Show me my account summary"
Claude: [Uses get_account_summary tool to fetch your data]

User: "Create a new sales pipeline using GPT-4"
Claude: [Uses get_pipeline_options and create_pipeline tools]

Testing the Connection

You can test the bridge manually:

# Set your API key
export GENUDO_API_KEY="your_api_key_here"

# Run the bridge
node index.js

# Send a test message (paste this and press Enter):
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}

# You should receive a response with server info

Troubleshooting

"GENUDO_API_KEY environment variable is required"

• Make sure you've set the API key in your Claude Code config
• Verify the API key is valid in your Genudo account

"Timeout waiting for endpoint from SSE"

• Check that GENUDO_BASE_URL is correct (defaults to https://api.genudo.ai)
• Verify your server is running and accessible
• Check firewall/network settings

"HTTP 401: Unauthorized"

• Your API key is invalid or expired
• Generate a new API key in your Genudo account settings

Connection Issues with Self-Signed Certificates

• The bridge is configured to accept self-signed certificates for local development
• For production, use proper SSL certificates

Environment Variables

Development

Project Structure

genudo-mcp-client/
├── index.js           # Main bridge script
├── package.json       # Node.js project config
├── .env.example       # Environment variables template
└── README.md          # This file

How It Works

1. Bridge connects to SSE endpoint to get the message POST URL
2. Reads JSON-RPC requests from stdin (from Claude Code)
3. Forwards requests as HTTP POST to the Genudo server
4. Returns responses via stdout back to Claude Code

Claude Code → (stdin) → Bridge → (HTTPS) → Genudo MCP Server
                ↑                              ↓
                └─────── (stdout) ←────────────┘

Security Notes

• Never commit your API key to version control
• Store API keys securely (environment variables, secrets manager)
• Rotate API keys regularly
• Use HTTPS in production
• Limit API key permissions to minimum required access

License

MIT

Support

Need help? We're here for you:

• 📖 Documentation
• 💬 Community Forum
• 🐛 Report an Issue
• 📧 Email Support

Contributing

We welcome contributions! Please see CONTRIBUTING.md for details on how to get started.

Quick overview:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

Changelog

See the GitHub Releases page for changes and version history.

Related Projects

• Genudo - The main Genudo automation platform
• Model Context Protocol - Learn more about MCP
• Claude Code - The Claude AI coding assistant