使用说明
Maesn Mcp Server
Maesn's official MCP (Model Context Protocol) server built with Nx, designed to connect to Maesn’s unified backend API. This server enables tools to retrieve accounting data like customers, invoices, bills, and accounts through structured, authenticated requests.
🚀 Features
- ⚡ Fast, scalable Nx + TypeScript setup
- 🧰 Pre-integrated with Maesn’s Unified API via MCP
- 🧪 Ready-to-use tools: customers, invoices, bills, accounts
📦 Installation
git clone https://github.com/YOUR_ORG/maesn-mcp.git
cd maesn-mcp
npm install
⚙️ Setup
Prerequisites
Before running the Maesn MCP server locally, ensure you have the following:
-
🔐 A Maesn API key
You can create an account and generate your API key via the Maesn Developer Portal. -
🧱 Node.js (v16 or later)
We recommend using Node.js v20+ for best compatibility. Download it from nodejs.org. -
🧰 Nx CLI (optional but helpful)
Nx is used to manage and run the workspace. Install it globally for easier use:npm install -g nx
MCP Configuration (e.g. Claude integration)
To connect your Maesn MCP server to an MCP-compatible environment (like Claude Desktop), download and install Claude, then follow these steps:
- Locate the configuration file on your machine. For Claude Desktop, this is typically:
- Windows:
%APPDATA%/Claude/claude_desktop_configuration.json - macOS:
~/Library/Application Support/Claude/claude_desktop_configuration.json - Linux:
~/.config/Claude/claude_desktop_configuration.json
- Add the following entry to the
mcpServerssection of the file:
{
"mcpServers": {
"maesn-mcp": {
"command": "node",
"args": [
"<ABSOLUTE_PATH>/apps/maesn-mcp/dist/main.js"
]
}
}
}
🔁 Replace <ABSOLUTE_PATH> with the full local path to your built MCP server.
Environment Variable Configuration
Create a .env file in the project root with your credentials:
Setup:
- Create your
.envfrom the example:
cp .env.example .env
- Fill in your credentials:
API_KEY=your_maesn_api_key
ACCOUNT_KEY=your_maesn_account_key
⚠️ Claude Desktop has a known bug where
envvariables inclaude_desktop_config.jsonare not reliably injected — this is why the.envapproach is used. If you are using a different MCP-compatible client that correctly injects environment variables, you may pass them natively instead.
🛠 Run Locally
After cloning the project, install dependencies:
npm install
Then start the dev server:
npx nx serve maesn-mcp
Available Resources
The MCP server is still under development, but most resources supported in the Unified API are already fully available through our MCP. Below is the list of currently supported resources:
- Accounts
- Async tasks
- Bills
- Booking proposals
- Contacts
- Customers
- Dimensions
- Document extensions
- Expenses
- Goods receipts
- Invoices
- Items
- Journal entries
- Journals
- Offers
- Payments
- Payment terms
- Projects
- Purchase orders
- Sales orders
- Suppliers
- Tax rates
- Trial balance
- Units
- Vendor credits
⚠️ Note: File support is not yet available. Additional resources and tools will be added incrementally.
📬 Contact Us
Have questions, need help, or want to explore what Maesn can do for you? We're here to help.
🌐 Learn More
- Visit our website: maesn.com
- Explore the unified API: Maesn API Documentation
🤝 Get in Touch
- 📧 Email: contact@maesn.com
- 💬 Book a demo: maesn.com/contact
