Which integrations are available for this server?

Enables sending generated invoices via email by configuring Gmail's SMTP server settings.

How do I use Invoice MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Invoice MCP Server generate an invoice for 5 consulting hours at $150/hr and email it to client@example.com" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Invoice MCP Server

by kmexnx

Overview Schema Related Servers Score Discussions

TypeScript

Hybrid

Invoice MCP Server

A Model Context Protocol (MCP) server for generating professional invoices as PDFs or sending them via email. This server provides tools that allow Claude to create, customize, and distribute invoices based on a professional template.

🚀 Quick Start

Option 1: NPX (Recommended)

Run directly without installation:

npx invoice-mcp-server

Option 2: Docker

# Pull and run
docker run -p 3000:3000 -v $(pwd)/invoices:/app/invoices invoice-mcp-server

# Or build locally
docker build -t invoice-mcp-server .
docker run -p 3000:3000 -v $(pwd)/invoices:/app/invoices invoice-mcp-server

Option 3: Traditional Installation

git clone https://github.com/kmexnx/invoice-mcp-server.git
cd invoice-mcp-server
npm install
npm run build

Related MCP server: Invoices Generator MCP Server

✨ Features

📄 PDF Generation: Create professional invoices as PDF files
📧 Email Integration: Send invoices directly via email
🎨 Template-based: Uses a clean, professional invoice template
💼 Business Ready: Includes all standard invoice fields (tax rates, line items, etc.)
🔧 Customizable: Easy to modify template and styling
🐳 Docker Support: Run in containers for easy deployment
⚡ NPX Ready: No installation required with npx
📁 Smart Directory Handling: Automatic directory creation with fallbacks

📋 Prerequisites

For NPX/Local Installation:

Node.js 18+
For email functionality: SMTP server credentials

For Docker:

Docker installed
For email functionality: SMTP server credentials

🛠️ Installation & Setup

Method 1: NPX (Zero Installation)

The easiest way to get started:

# Run directly
npx invoice-mcp-server

# With custom output directory
OUTPUT_DIR=/Users/yourname/Documents/invoices npx invoice-mcp-server

# With environment variables
SMTP_HOST=smtp.gmail.com SMTP_USER=you@gmail.com OUTPUT_DIR=/tmp/invoices npx invoice-mcp-server

Method 2: Docker Setup

Create a docker-compose.yml:

version: '3.8'
services:
  invoice-mcp:
    image: invoice-mcp-server
    ports:
      - "3000:3000"
    volumes:
      - ./invoices:/app/invoices
      - ./.env:/app/.env
    environment:
      - SMTP_HOST=smtp.gmail.com
      - SMTP_PORT=587
      - SMTP_USER=your-email@gmail.com
      - SMTP_PASS=your-app-password
      - FROM_EMAIL=your-email@gmail.com
      - FROM_NAME=Your Company Name
      - OUTPUT_DIR=/app/invoices

Run with Docker Compose:

docker-compose up -d

Method 3: Traditional Installation

Clone and install:

git clone https://github.com/kmexnx/invoice-mcp-server.git
cd invoice-mcp-server
npm install
npm run setup  # Creates directories and checks permissions

Configure environment:

cp .env.example .env
# Edit .env with your settings

Build and run:

npm run build
npm start

📁 Directory Configuration

The server needs a directory to save generated PDF invoices. It uses this priority order:

Custom Directory (Recommended): Set OUTPUT_DIR environment variable
Default Local: ./invoices in current directory
Fallback: System temporary directory

Setting Custom Output Directory

For NPX users:

# Set for current session
export OUTPUT_DIR=/Users/yourname/Documents/invoices
npx invoice-mcp-server

# Or inline
OUTPUT_DIR=/path/to/your/invoices npx invoice-mcp-server

For permanent setup:

Add to your shell profile (~/.zshrc, ~/.bashrc, etc.):

export OUTPUT_DIR=/Users/yourname/Documents/invoices

For Docker users:

docker run -e OUTPUT_DIR=/app/invoices -v /your/local/path:/app/invoices invoice-mcp-server

Directory Permissions

The server automatically:

✅ Creates the output directory if it doesn't exist
✅ Tests write permissions
✅ Falls back to temporary directories if needed
✅ Provides clear error messages

If you encounter permission issues:

# Create and set permissions manually
mkdir -p /path/to/your/invoices
chmod 755 /path/to/your/invoices

# Or use a directory you own
export OUTPUT_DIR=$HOME/Documents/invoices

🔧 Claude Desktop Configuration

Add this server to your Claude Desktop configuration:

For NPX Usage:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "invoice-server": {
      "command": "npx",
      "args": ["invoice-mcp-server"],
      "env": {
        "OUTPUT_DIR": "/Users/yourname/Documents/invoices",
        "SMTP_HOST": "smtp.gmail.com",
        "SMTP_PORT": "587",
        "SMTP_USER": "your-email@gmail.com",
        "SMTP_PASS": "your-app-password",
        "FROM_EMAIL": "your-email@gmail.com",
        "FROM_NAME": "Your Company Name"
      }
    }
  }
}

For Docker Usage:

{
  "mcpServers": {
    "invoice-server": {
      "command": "docker",
      "args": ["exec", "invoice-mcp-container", "node", "/app/dist/index.js"],
      "env": {
        "OUTPUT_DIR": "/app/invoices",
        "SMTP_HOST": "smtp.gmail.com",
        "SMTP_PORT": "587",
        "SMTP_USER": "your-email@gmail.com",
        "SMTP_PASS": "your-app-password"
      }
    }
  }
}

For Local Installation:

{
  "mcpServers": {
    "invoice-server": {
      "command": "node",
      "args": ["/path/to/invoice-mcp-server/dist/index.js"],
      "env": {
        "OUTPUT_DIR": "/Users/yourname/Documents/invoices",
        "SMTP_HOST": "smtp.gmail.com",
        "SMTP_PORT": "587",
        "SMTP_USER": "your-email@gmail.com",
        "SMTP_PASS": "your-app-password"
      }
    }
  }
}

💬 Usage Examples

Basic Invoice Creation

Claude, create me an invoice for "Acme Corp" for the amount of $5000

Detailed Invoice

Claude, create an invoice with the following details:
- Client: TechStart Inc.
- Services: Web Development (40 hours at $125/hour), Logo Design ($500)
- Tax rate: 8.5%
- Due date: 30 days from today
- Save as PDF and email to client@techstart.com

Multiple Line Items

Claude, generate an invoice for:
- Company: Global Solutions LLC
- Item 1: Consulting Services - $2,500
- Item 2: Project Management - $1,200
- Item 3: Documentation - $800
- Tax rate: 7.25%
- Email it to accounting@globalsolutions.com

🛠️ Available Tools

1. `create_invoice_pdf`

Generates a PDF invoice file.

Parameters:

invoice_data: Complete invoice information
filename: Optional custom filename

2. `send_invoice_email`

Creates and sends an invoice via email.

Parameters:

invoice_data: Complete invoice information
recipient_email: Email address to send to
subject: Optional custom email subject
message: Optional custom email message

3. `get_invoice_template`

Returns the current invoice template structure for reference.

📊 Invoice Data Structure

{
  // Company Information
  company: {
    name: string;
    address: string;
    city: string;
    state: string;
    zipCode: string;
    phone?: string;
    fax?: string;
    email?: string;
  };
  
  // Client Information
  billTo: {
    name: string;
    company?: string;
    address: string;
    city: string;
    state: string;
    zipCode: string;
    phone?: string;
  };
  
  // Invoice Details
  invoiceNumber: string;
  date: string;
  dueDate?: string;
  
  // Line Items
  items: Array<{
    description: string;
    amount: number;
  }>;
  
  // Financial Details
  taxRate?: number; // as percentage (e.g., 8.5 for 8.5%)
  other?: number;   // additional fees/discounts
}

🔍 Environment Variables

Variable	Description	Required	Default	Example
`OUTPUT_DIR`	PDF output directory	Recommended	`./invoices`	`/Users/name/Documents/invoices`
`SMTP_HOST`	SMTP server host	No*	-	`smtp.gmail.com`
`SMTP_PORT`	SMTP server port	No	`587`	`587`
`SMTP_USER`	SMTP username	No*	-	`you@gmail.com`
`SMTP_PASS`	SMTP password	No*	-	`your-app-password`
`FROM_EMAIL`	From email address	No	`SMTP_USER`	`billing@company.com`
`FROM_NAME`	From name	No	-	`Your Company Name`
`TEMP_DIR`	Temporary files directory	No	System temp	`/tmp`

*Required only for email functionality

Important Notes:

OUTPUT_DIR: Highly recommended to set this to avoid permission issues
SMTP credentials: Only needed if you want to email invoices
Paths: Use absolute paths for best results
Permissions: Ensure the OUTPUT_DIR is writable

🐳 Docker Configuration

Dockerfile

FROM node:18-alpine

WORKDIR /app

COPY package*.json ./
RUN npm ci --only=production

COPY dist ./dist
COPY .env.example ./.env

RUN mkdir -p invoices

EXPOSE 3000

CMD ["node", "dist/index.js"]

Docker Environment

# Run with environment variables
docker run -e SMTP_HOST=smtp.gmail.com \
           -e SMTP_USER=you@gmail.com \
           -e SMTP_PASS=yourpassword \
           -e OUTPUT_DIR=/app/invoices \
           -v $(pwd)/invoices:/app/invoices \
           invoice-mcp-server

🧪 Development

Project Structure

invoice-mcp-server/
├── src/
│   ├── index.ts              # Main MCP server
│   ├── invoice-generator.ts  # PDF generation logic
│   ├── email-service.ts      # Email functionality
│   ├── invoice-template.ts   # HTML template
│   └── setup.js             # Setup script
├── dist/                     # Compiled JavaScript
├── invoices/                 # Generated PDFs (created by setup)
├── Dockerfile               # Docker configuration
├── docker-compose.yml       # Docker Compose setup
├── package.json
└── README.md

NPM Scripts

npm run build      # Compile TypeScript
npm run dev        # Development mode with watch
npm start          # Run compiled server
npm run setup      # Create directories and check setup
npm run clean      # Clean build directory
npm run docker     # Build Docker image

Testing

Test the server using the MCP inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Setup Script

The setup script (npm run setup) will:

✅ Create necessary directories
✅ Test write permissions
✅ Check Node.js version
✅ Verify package structure
✅ Display helpful diagnostics

🐛 Troubleshooting

Common Issues

Directory Permission Errors

# Solution 1: Set custom directory
export OUTPUT_DIR=/Users/yourname/Documents/invoices
mkdir -p $OUTPUT_DIR

# Solution 2: Use setup script
npm run setup

# Solution 3: Use temporary directory
export OUTPUT_DIR=/tmp/invoices

NPX Issues

Package not found: Ensure you have npm 5.2+ for npx support
Permission errors: Try setting OUTPUT_DIR to a directory you own
Directory creation fails: Use OUTPUT_DIR=/tmp/invoices npx invoice-mcp-server

Docker Issues

Port conflicts: Change port mapping -p 3001:3000
Volume issues: Ensure local directories exist and are writable
Memory limits: Increase Docker memory for large invoices

Email Issues

Gmail: Use App Passwords instead of regular password
SMTP Errors: Verify host, port, and credentials
Firewall: Ensure SMTP ports aren't blocked

PDF Generation Issues

Missing fonts: Install system fonts or use web fonts
Memory issues: Increase Node.js memory limit
Puppeteer errors: Install Chrome dependencies

Debug Mode

Enable debug logging:

DEBUG=invoice-mcp:* npx invoice-mcp-server

Environment Diagnostics

Run the setup script to diagnose issues:

npm run setup

This will show:

✅ Directory creation status
✅ Write permissions
✅ Node.js version
✅ Environment information
✅ Troubleshooting suggestions

📈 Performance

Optimization Tips

Use custom OUTPUT_DIR for faster file access
Docker multi-stage builds for smaller images
PDF caching for repeated templates
Email queuing for bulk operations
Resource limits for container deployments

Scaling

Use Redis for session storage
Implement queue system for PDF generation
Load balance multiple containers
Use external SMTP service

🤝 Contributing

Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request

📄 License

MIT License - see LICENSE file for details.

🆘 Support

📋 Issues: GitHub Issues
📖 Examples: See EXAMPLES.md
📚 MCP Docs: MCP Documentation
🐳 Docker: Docker Hub

Quick Start Example:

Set your directory: export OUTPUT_DIR=/Users/yourname/Documents/invoices
Run: npx invoice-mcp-server
Configure Claude Desktop (see above)
Ask Claude: "Create an invoice for ABC Company for $2,500"
Claude handles the rest automatically! 🎉

The server handles all formatting, calculations, and delivery automatically while saving PDFs to your specified directory.

Available Tools

3 tools

create_invoice_pdfC

Generate a PDF invoice file

ParametersJSON Schema

Name	Required	Description	Default
`invoice_data`	Yes	Complete invoice data including company info, bill-to info, items, etc.
`filename`	No	Optional custom filename for the PDF (without .pdf extension)

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full disclosure burden but only states the basic action. It fails to specify where the generated file is stored (returned as binary, saved to disk, etc.), whether it overwrites existing files, or any idempotency characteristics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief (5 words) and front-loaded with the action verb. No wasted words or redundancy, though the extreme brevity contributes to the lack of behavioral and contextual detail given the absence of annotations and output schemas.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a file-generation tool with nested parameters, no annotations, and no output schema. The description fails to hint at return values (file path vs. binary data) or explain relationships to sibling tools, leaving significant gaps in the agent's understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage, establishing a baseline of 3. The description adds no additional parameter context beyond what the schema already provides (e.g., no details on invoice_data structure or formatting constraints).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific action (Generate) and resource (PDF invoice file). Clear and direct, though it does not explicitly differentiate from sibling tools like get_invoice_template or send_invoice_email.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this tool versus alternatives (e.g., when to generate a PDF vs. sending an email or retrieving a template). No prerequisites or workflow context is mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_invoice_templateB

Get the current invoice template structure for reference

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must carry full burden. While 'Get' implies read-only and 'current' suggests temporal relevance, the description fails to disclose side effects, authentication requirements, rate limits, or what the 'structure' actually contains (fields, schema, etc.).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single 9-word sentence is appropriately front-loaded with the action verb. However, given the absence of annotations and output schema, the extreme brevity leaves significant gaps rather than demonstrating efficient completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should specify what the template structure includes or its format. 'Structure for reference' is vague and insufficient for an agent to predict the return value or utility of calling this tool before creating PDFs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0 parameters with 100% coverage. Per guidelines, 0 params = baseline 4. The description does not mention parameters (none exist), which is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses specific verb 'Get' and resource 'invoice template structure'. Clearly identifies the operation and target resource, though it does not explicitly differentiate from siblings 'create_invoice_pdf' or 'send_invoice_email' in the description text (distinction relies on tool names).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no guidance on when to use this tool versus the sibling tools. No mention of workflow sequence (e.g., whether to call this before create_invoice_pdf) or prerequisites. The phase 'for reference' hints at read-only usage but doesn't establish clear usage boundaries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

send_invoice_emailC

Create and send an invoice via email

ParametersJSON Schema

Name	Required	Description
`invoice_data`	Yes	Complete invoice data including company info, bill-to info, items, etc.
`recipient_email`	Yes	Email address to send the invoice to
`subject`	No	Optional custom email subject
`message`	No	Optional custom email message body

TDQS

C2.6/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but fails to disclose critical behavioral traits: that sending email triggers external irreversible actions, potential for duplicate sends if retried, delivery status limitations, or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at seven words with no redundancy. However, the brevity constitutes under-specification rather than efficient information density given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a 4-parameter mutation tool with nested objects and external side effects. No output schema, no annotations, and minimal description leaves significant gaps in understanding prerequisites, error cases, and return behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for all four parameters. The tool description adds no parameter-specific guidance beyond the schema, which warrants the baseline score of 3 for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the core action (create and send) and medium (email), but lacks specificity about the invoice content/structure and does not explicitly differentiate from sibling 'create_invoice_pdf' which presumably also creates invoices but does not send them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this versus 'create_invoice_pdf' or prerequisites like invoice validation. No mention of idempotency concerns for email sending or retry behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.2Apr 1, 2026
- First observedcreate_invoice_pdf
- First observedget_invoice_template
- First observedsend_invoice_email

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: create_invoice_pdf generates a PDF file, get_invoice_template retrieves template structure, and send_invoice_email handles email delivery. There is no overlap in functionality, making tool selection unambiguous for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (create_invoice_pdf, get_invoice_template, send_invoice_email) with clear verbs and descriptive nouns. The naming is uniform and predictable throughout the set.

Tool Count3/5

With only 3 tools, the set feels thin for an invoice management server, lacking operations like updating, deleting, or listing invoices. While the tools cover core actions, the count is borderline low for typical domain coverage.

Completeness2/5

The tool set has significant gaps for invoice management: it includes creation, template retrieval, and email sending, but misses essential CRUD operations (e.g., list_invoices, update_invoice, delete_invoice) and other lifecycle steps like payment tracking or status updates, which could lead to agent failures in workflows.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

I Hate InvoicingOAuth
io.ihateinvoicing
Send invoices from Claude and ChatGPT. One sentence becomes a PDF with a Stripe payment link.
Payments & Billing Finance App Automation
2
invoice-pdf-billing-generator
io.github.theluckystrike
Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.
Payments & Billing Finance
1
PDFMakerAPI A
io.github.GerardoBarrera
Turn a description into a shareable, editable PDF — invoices, certificates, reports, resumes.
Developer Tools Workplace & Productivity
2
Slipstack PDF A
dev.slipstack
Generate invoice and receipt PDFs from JSON. Agent-callable document API with a free demo quota.
Payments & Billing Finance Developer Tools
2

Related MCP Servers

mad-invoice-mcp
Finance File Systems
mad-sol-dev
A
license
Not graded
quality
D
maintenance
Enables creation and management of invoices with JSON storage and LaTeX-based PDF rendering. Supports draft creation and professional PDF generation through customizable LaTeX templates.
Updated 8 months ago (2025-12-30 18:36 UTC)
Apache 2.0
Invoices Generator MCP Server
Finance E-commerce & Retail App Automation
BACH-AI-Tools
A
license
C
quality
D
maintenance
Provides access to the Invoices Generator API to create professional, customizable invoices with detailed buyer, seller, and service information. It supports multiple languages, currencies, and tax configurations through a standardized tool interface.
Updated 9 months ago (2025-12-07 19:50 UTC)
1
MIT
Wave MCP Server
Finance Payments & Billing
LightningBerk
A
license
Not graded
quality
D
maintenance
Enables Wave invoicing operations including listing invoices, retrieving details, and generating branded PDFs directly from AI assistants.
Updated 7 months ago (2026-01-28 17:07 UTC)
21
ISC
Italy Invoice MCP
Payments & Billing Finance Legal & Compliance
junter1989k-ai
A
license
Not graded
quality
B
maintenance
Enables AI agents to issue Italian FatturaPA electronic invoices and transmit them to the SdI via Invoicetronic. Supports creating and querying invoices with Italian VAT rates.
Updated 2 months ago (2026-07-11 05:46 UTC)
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kmexnx/invoice-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Invoice MCP Server

🚀 Quick Start

Option 1: NPX (Recommended)

Option 2: Docker

Option 3: Traditional Installation

✨ Features

📋 Prerequisites

For NPX/Local Installation:

For Docker:

🛠️ Installation & Setup

Method 1: NPX (Zero Installation)

Method 2: Docker Setup

Method 3: Traditional Installation

📁 Directory Configuration

Setting Custom Output Directory

For NPX users:

For permanent setup:

For Docker users:

Directory Permissions

🔧 Claude Desktop Configuration

For NPX Usage:

For Docker Usage:

For Local Installation:

💬 Usage Examples

Basic Invoice Creation

Detailed Invoice

Multiple Line Items

🛠️ Available Tools

1. create_invoice_pdf

2. send_invoice_email

3. get_invoice_template

📊 Invoice Data Structure

🔍 Environment Variables

Important Notes:

🐳 Docker Configuration

Dockerfile

Docker Environment

🧪 Development

Project Structure

NPM Scripts

Testing

Setup Script

🐛 Troubleshooting

Common Issues

Directory Permission Errors

NPX Issues

Docker Issues

Email Issues

PDF Generation Issues

Debug Mode

Environment Diagnostics

📈 Performance

Optimization Tips

Scaling

🤝 Contributing

📄 License

🆘 Support

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

1. `create_invoice_pdf`

2. `send_invoice_email`

3. `get_invoice_template`