Libs MCP Service
# Libs MCP Service
A Model Context Protocol (MCP) service for integration with external platforms. This service provides CRUD operations for various entities through a standardized MCP interface using the official MCP SDK.
## Quick Setup
### Configuration
Add the following to your MCP configuration:
```json
{
"mcpServers": {
"libs-mcp-service": {
"command": "npx",
"args": ["github:AdminRHS/libs-mcp-service"],
"env": {
"API_TOKEN": "your_actual_token_here",
"API_BASE_URL": "https://libs.anyemp.com",
"MODE": "light"
}
}
}
}
```
**Important**: Replace `your_actual_token_here` with your real API token from the external platform.
### Environment Variables
| Variable | Required | Description | Default |
|----------|----------|-------------|---------|
| `API_TOKEN` | Yes | Authentication token for the external platform | - |
| `API_BASE_URL` | Yes | Base URL for the external API | - |
| `MODE` | No | UI mode: `light` (minimal) or `standard` (full). Affects tool list and response shape | `standard` |
### API Environments
- **Production**: `https://libs.anyemp.com` - Main microservice for libraries
- **Development**: `https://libdev.anyemp.com` - Recommended for development and testing
**Recommendation**: Use the development environment for testing to avoid affecting production data.
## โจ Features
- **๐ข Official MCP SDK**: Full MCP compliance using `@modelcontextprotocol/sdk`
- **๐ง Universal Tools**: `list`, `get`, `create`, `update` for all 20+ entity types
- **โก Performance**: Response caching with TTL and smart invalidation
- **๐ก๏ธ Security**: Rate limiting, request size caps, and bearer token authentication
- **๐ Smart Updates**: Automatic term preservation in update operations
- **๐ค AI Metadata**: Comprehensive tracking for AI-generated content
- **๐ฑ Dual Modes**: Light mode for minimal UIs, standard mode for full functionality
- **๐ Easy Deployment**: Executable via npx without local installation
## ๐๏ธ Modes
Configure behavior with the `MODE` environment variable:
### Light Mode (`MODE=light`)
- **Same tool list**: All tools available (no filtering)
- **Auto-optimization**: List operations automatically add `all=true` and `isShort=true` parameters
- **Reduced responses**: Single `get` operations return `{ id, name }` format
- **Perfect for**: Claude, ChatGPT, and other token-conscious clients
### Standard Mode (`MODE=standard`)
- **Full tool list**: All available tools shown
- **Complete responses**: Full entity payloads in all operations
- **Manual control**: Explicit parameters required for optimization
- **Perfect for**: Development and full-featured applications
## ๐ ๏ธ Available Tools
### Universal Tools (All Entities)
- **`list`** โ List entities with pagination and search
- **`get`** โ Fetch single entity by ID
- **`create`** โ Create new entity with AI metadata support
- **`update`** โ Update entity with automatic term preservation
### Essential Specialized Tools
- **`get_term_types`** โ Retrieve available term types
- **`get_priorities`** โ Retrieve all priorities
- **`find_existing_responsibility_terms`** โ Check existing action-object term combinations
- **`create_term`** โ Create individual terms with AI metadata
- **`update_term`** โ Update individual terms with AI metadata
AI metadata behavior:
- Create: include `aiMetadata` only for the term(s) you want marked/recorded as AI-generated; others remain unchanged.
- Update: include `aiMetadata` only for term(s) you intend to change; omitting it leaves existing AI fields as-is.
### Supported Entities (23 Types)
- **Core**: Departments, Professions, Languages, Countries, Cities
- **Content**: Actions, Objects, Responsibilities, Formats
- **Organization**: Industries, Sub-Industries, Tools, Tool Types
- **System**: Statuses, Term Types, Individual Terms
- **Management**: Shifts, Currencies, Rates, Levels, Positions, Skills, Priorities
## ๐ Common Usage Patterns
### List Entities with Search
```javascript
// List departments with search
{
"resource": "departments",
"search": "engineering",
"limit": 5
}
```
### Create Entity with AI Metadata
```javascript
// Create department with AI tracking
{
"resource": "departments",
"payload": {
"mainTerm": {
"value": "Data Science",
"language_id": 1,
"term_type_id": 1,
"aiMetadata": {
"ai_generated": true,
"ai_model": "gpt-4o",
"ai_confidence_score": 9.5
}
}
}
}
```
### Update with Term Preservation
```javascript
// Update preserves existing terms automatically
{
"resource": "departments",
"id": "123",
"payload": {
"mainTerm": {
"value": "Updated Name",
"language_id": 1,
"term_type_id": 1
}
// Existing terms automatically preserved
}
}
```
## ๐๏ธ Architecture
### Core Components
- **`index.js`** - Main MCP server with official SDK integration
- **`config.js`** - Environment validation and configuration
- **`api.js`** - HTTP client with caching, timeouts, and error handling
- **`entities.js`** - CRUD operations for all 23 entity types
- **`tools.js`** - MCP tool definitions with JSON Schema validation
- **`handlers.js`** - Tool handler mappings and routing
### Advanced Features
- **`src/errors.js`** - Structured error handling with MCP formatting
- **`src/cache.js`** - Response caching with TTL and smart invalidation
- **`src/rateLimit.js`** - Fixed-window rate limiting per client
### Build System
- **`libs-mcp-service.js`** - Bundled executable (530KB) for npx deployment
## ๐งช Testing Status
### โ
Comprehensive Testing Complete (23/23 Entities)
| Entity Category | Entities | Status | Features Tested |
|----------------|----------|--------|-----------------|
| **Core** | Departments, Professions, Languages | โ
Complete | CRUD, AI metadata, term preservation |
| **Geography** | Countries, Cities | โ
Complete | Complex terms, ISO codes, coordinates |
| **Content** | Actions, Objects, Responsibilities | โ
Complete | Term relationships, format linking |
| **Organization** | Industries, Sub-Industries | โ
Complete | Parent-child relationships |
| **System** | Tools, Tool Types, Formats | โ
Complete | Many-to-many relationships |
| **Meta** | Statuses, Term Types, Terms | โ
Complete | Individual term management |
| **Management** | Shifts, Currencies, Rates, Levels, Positions, Skills, Priorities | โ
Complete | Time, financial, position, role, skill, and priority management |
### Key Testing Results
- **โ
Schema Validation**: All entity schemas validated against actual API
- **โ
Permission Testing**: Proper 403 handling for restricted operations
- **โ
AI Metadata**: Comprehensive testing of AI tracking fields
- **โ
Term Preservation**: Smart update logic maintains existing terms
- **โ
Relationship Handling**: Complex entity relationships working correctly
- **โ
Error Handling**: Structured errors with proper MCP formatting
## ๐ Security Features
- **๐ก๏ธ Bearer Authentication**: Secure API token handling
- **โฑ๏ธ Rate Limiting**: 60 requests/minute per client (configurable)
- **๐ Request Size Limits**: 100KB body size cap
- **๐ Secret Masking**: Authorization headers masked in cache keys
- **โฐ Timeout Protection**: 30-second request timeouts with AbortController
## ๐ Performance Optimizations
- **๐พ Response Caching**: 5-minute TTL with smart invalidation
- **๐๏ธ Cache Management**: Automatic prefix-based invalidation on writes
- **๐ฆ Bundle Optimization**: Minified 530KB bundle with tree-shaking
- **โก Efficient Updates**: Term preservation reduces API calls
## ๐ Installation & Deployment
### Option 1: Direct Execution (Recommended)
```bash
npx github:AdminRHS/libs-mcp-service
```
### Option 2: Global Installation
```bash
npm install -g github:AdminRHS/libs-mcp-service
libs-mcp-service
```
### Option 3: Development Mode
```bash
git clone https://github.com/AdminRHS/libs-mcp-service.git
cd libs-mcp-service
npm install
npm run dev
```
## ๐ง API Integration
The service expects RESTful endpoints following this pattern:
```
GET /api/token/{entity} # List with pagination
GET /api/token/{entity}/:id # Get by ID
POST /api/token/{entity} # Create new
PUT /api/token/{entity}/:id # Update existing
DELETE /api/token/{entity}/:id # Delete (where permitted)
```
All requests include `Authorization: Bearer <API_TOKEN>` header.
### Supported Endpoints
- `/api/token/departments` - Department management
- `/api/token/professions` - Profession management
- `/api/token/languages` - Language and term management
- `/api/token/countries` - Country data with ISO codes
- `/api/token/cities` - City data with coordinates
- `/api/token/actions` - Action definitions with terms
- `/api/token/objects` - Object definitions with formats
- `/api/token/responsibilities` - Responsibility linking
- `/api/token/industries` - Industry classifications
- `/api/token/sub-industries` - Sub-industry definitions
- `/api/token/tools` - Tool management with types
- `/api/token/tool-types` - Tool type definitions
- `/api/token/formats` - Format specifications
- `/api/token/statuses` - Status management
- `/api/token/priorities` - Priority management
- `/api/token/term-types` - Term type definitions
- `/api/token/terms` - Individual term management
- `/api/token/shifts` - Working time management
- `/api/token/currencies` - Currency management
- `/api/token/rates` - Rate management
- `/api/token/levels` - Position level management
- `/api/token/positions` - Position and role management
- `/api/token/skills` - Skill management (responsibility-tool relationships)
## ๐ Troubleshooting
### Common Issues
**โ "API_TOKEN environment variable is required"**
- Verify API_TOKEN is set in your MCP client configuration
- Check for typos in environment variable names
**โ "HTTP error! status: 401"**
- Verify your API token is valid and not expired
- Ensure proper Bearer token format
**โ "HTTP error! status: 403"**
- Normal behavior for write operations on most entities
- Only certain entities allow POST/PUT operations
**โ "Rate limit exceeded"**
- Check if multiple clients are using same configuration
**โ Service not starting**
- Ensure Node.js 18+ is installed
- Check network connectivity to API_BASE_URL
### Debug Mode
Enable detailed logging:
```bash
DEBUG=* npx github:AdminRHS/libs-mcp-service
```
### Health Check
Test connectivity:
```javascript
// Use 'list' tool with minimal parameters
{
"resource": "term_types",
"limit": 1
}
```
## ๐ Metrics & Monitoring
The service includes built-in metrics tracking:
- **Request counts** by tool and entity type
- **Error rates** with status code breakdown
- **Cache hit/miss ratios** for performance monitoring
- **Rate limit statistics** per client
- **Response times** for performance analysis
## ๐ค AI Metadata Support
Comprehensive AI tracking for all terms and entities:
### Supported Fields
- `ai_generated` - Whether content was AI-generated
- `ai_model` - AI model used (e.g., "gpt-4o", "claude-3.5")
- `ai_confidence_score` - Confidence rating (0.00-9.99)
- `ai_quality_score` - Quality assessment (0.00-9.99)
- `ai_validation_status` - Review status ("pending", "approved", "rejected")
- `ai_human_reviewed` - Human review flag
- `ai_source_data` - Original source information
- `ai_metadata` - Additional AI-specific data
### Usage Examples
See `docs-models/AI_METADATA_GUIDE.md` for comprehensive examples and best practices.
## ๐ License
MIT License - see LICENSE file for details.
## ๐ค Contributing
1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Make your changes
4. Run `npm run build` to update the bundled file
5. Commit both source and bundled files
6. Submit a pull request
## ๐ Support
- **Issues**: Create an issue on GitHub
- **Documentation**: Check the `docs-models/` directory
- **API Questions**: Verify API_BASE_URL and token configuration
- **Performance**: Monitor cache hit rates and adjust TTL settings
---
**Status**: โ
**Production Ready** - All 23 entities tested and validated
Built with โค๏ธ using the official Model Context Protocol SDK
TDQS
Scored across 11 tools
Generic tools like list/get/create/update overlap with specialized tools like get_priority, create_term, and update_term, making it unclear whether to use the generic path or the specialized one for term and priority operations. Descriptions help clarify intent, but the boundaries are not crisp.
The generic operations use bare verbs (list, get, create, update) while the specialized operations use verb_noun patterns (get_priority, create_term, find_existing_skill_terms), so the naming convention is mixed. All names are readable and consistently snake_case, but the pattern is not uniform.
Eleven tools is a reasonable count for an entity/term management server, covering generic resource operations plus dedicated priority, term type, and lookup helpers. Each tool appears purposeful and the set is not bloated.
The tool surface covers list, get, create, and update operations, but there is no delete operation for entities or terms, which leaves the lifecycle incomplete. The find_existing_* helpers partially cover term discovery, but dedicated term listing/retrieval is still somewhat implicit.