Zenskar MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with access to the Zenskar API for customer management, invoicing, and billing operations.

Features

• Customer Management: List, search, create, and update customers
• Invoice Operations: Create, retrieve, and manage invoices
• Subscription Management: Handle subscription lifecycle
• Billing Operations: Process payments and manage billing
• Multi-tenant Support: Organization-based access control
• Secure Authentication: Bearer token authentication

Installation

For Claude Desktop App

Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "zenskar": {
      "command": "npx",
      "args": ["mcp-zenskar"],
      "env": {
        "ZENSKAR_ORGANIZATION": "your-org-id",
        "ZENSKAR_AUTH_TOKEN": "your-bearer-token"
      }
    }
  }
}

You can omit one or both environment variables from the config, but the server will error until Claude supplies them in a tool call. Keeping them in the env block prevents repeated credential prompts.

For Other AI Applications

Install globally:

npm install -g mcp-zenskar

Or run directly:

npx mcp-zenskar

Authentication

This MCP server requires two authentication parameters for every request:

1. Organization ID: Your Zenskar organization identifier
2. Authorization Token: Your API Bearer token

Getting Your Credentials

1. Organization ID: Available in your Zenskar dashboard settings
2. API Token: Generate from Zenskar dashboard → Settings → API Keys

At runtime the server looks for these values in the tool invocation first, then falls back to the ZENSKAR_ORGANIZATION and ZENSKAR_AUTH_TOKEN environment variables. Tokens that look like JWTs are sent as Authorization: Bearer ...; everything else is sent as an x-api-key header automatically.

Usage

In Claude Desktop

Once configured, you can ask Claude to interact with your Zenskar data:

"Show me my recent customers"
"Create an invoice for customer XYZ"
"List all active subscriptions"

Manual Tool Calls

Each tool requires authentication parameters:

{
  "organization": "your-org-id",
  "authorization": "Bearer your-token",
  // ... other tool-specific parameters
}

Available Tools

The server provides access to all Zenskar API endpoints including:

• listCustomers - Retrieve paginated customer lists
• getCustomer - Get specific customer details
• createCustomer - Create new customers
• updateCustomer - Update existing customers
• listInvoices - Retrieve invoice lists
• createInvoice - Generate new invoices
• getInvoice - Get invoice details
• And many more...

Security

• All API requests require valid organization ID and Bearer token
• Multi-tenant isolation ensures data privacy
• No credentials are stored by the MCP server
• All authentication is passed through from the client

Development

# Clone the repository
git clone https://github.com/your-org/mcp-zenskar
cd mcp-zenskar

# Install dependencies
npm install

# Run the server
npm start

Developing Locally Without Publishing

If you want Claude Desktop to use a local checkout instead of the npm package:

# Install dependencies once
npm install

# Optional: install the local build globally
npm install -g .

Then either point Claude to the globally-installed binary (usually $(npm bin -g)/mcp-zenskar) or call the repo copy directly:

{
  "command": "node",
  "args": ["/absolute/path/to/mcp-zenskar/src/server.js"],
  "env": {
    "ZENSKAR_ORGANIZATION": "your-org-id",
    "ZENSKAR_AUTH_TOKEN": "your-token"
  }
}

Configuration

The server uses src/mcp-config.json to define available tools and API endpoints. This file contains the complete mapping of MCP tools to Zenskar API operations.

License

MIT

Support

For issues and support:

• GitHub Issues: https://github.com/zenskar/mcp-zenskar/issues
• Zenskar Documentation: https://docs.zenskar.com