Package Exports
- @coretext-ai/qa-zendesk-b7c8d9e0-f1a2-4345-a678-789012345679
- @coretext-ai/qa-zendesk-b7c8d9e0-f1a2-4345-a678-789012345679/dist/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@coretext-ai/qa-zendesk-b7c8d9e0-f1a2-4345-a678-789012345679) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
zendesk-mcp-server
MCP server with zendesk integration
This MCP server was generated using the Template Orchestrator and includes the following integrations:
Zendesk Integration
Endpoints included: 22
zendesk_create_ticket: Create a new ticket with subject, description, and user informationzendesk_get_ticket: Retrieve detailed information about a specific ticketzendesk_update_ticket: Update an existing ticket with new field valueszendesk_delete_ticket: Delete a ticket permanentlyzendesk_list_tickets: List all tickets with optional filtering and paginationzendesk_search_tickets: Search tickets using query parameterszendesk_add_ticket_comment: Add a comment to an existing ticketzendesk_create_user: Create a new user in Zendeskzendesk_get_user: Retrieve detailed information about a specific userzendesk_update_user: Update an existing user's informationzendesk_list_users: List all users with optional paginationzendesk_search_users: Search users by email or namezendesk_create_organization: Create a new organization in Zendeskzendesk_get_organization: Retrieve detailed information about a specific organizationzendesk_update_organization: Update an existing organization's informationzendesk_list_organizations: List all organizations with optional paginationzendesk_list_groups: List all agent groupszendesk_get_group: Retrieve detailed information about a specific groupzendesk_bulk_update_tickets: Update multiple tickets at oncezendesk_get_ticket_comments: Get all comments for a specific ticketzendesk_get_ticket_metrics: Get metrics for a specific ticket (response times, resolution time, etc.)zendesk_get_ticket_events: Get all events for a specific ticket
Required environment variables:
ZENDESK_API_TOKENZENDESK_EMAILZENDESK_DOMAIN
Installation
npm install @coretext-ai/zendesk-mcp-serverEnvironment Setup
Create a .env file with the following variables:
ZENDESK_API_TOKEN=your_zendesk_api_token_here
ZENDESK_EMAIL=your_zendesk_email_here
ZENDESK_DOMAIN=your_zendesk_domain_here
# Centralized Log Shipping Configuration
LOG_SHIPPING_ENABLED=true
LOG_INGESTION_URL=https://your-log-endpoint.execute-api.region.amazonaws.com/dev/logs
LOG_INGESTION_API_KEY=your_api_key_here
CORETEXT_USER=your_user_id_here
LOG_LEVEL=ERROR
LOG_SHIPPING_BATCH_SIZE=500
LOG_SHIPPING_INTERVAL=5000
LOG_SHIPPING_MAX_RETRIES=3Usage
Running the server
# Development mode
npm run dev
# Production mode
npm run build && npm startUsing with Claude Desktop
Add this to your Claude Desktop configuration:
{
"mcpServers": {
"zendesk-mcp-server": {
"command": "npx",
"args": ["@coretext-ai/zendesk-mcp-server"]
}
}
}Available Tools
This server provides 22 tools across 1 integrations:
Zendesk Tools
- zendesk_create_ticket: Create a new ticket with subject, description, and user information
- zendesk_get_ticket: Retrieve detailed information about a specific ticket
- zendesk_update_ticket: Update an existing ticket with new field values
- zendesk_delete_ticket: Delete a ticket permanently
- zendesk_list_tickets: List all tickets with optional filtering and pagination
- zendesk_search_tickets: Search tickets using query parameters
- zendesk_add_ticket_comment: Add a comment to an existing ticket
- zendesk_create_user: Create a new user in Zendesk
- zendesk_get_user: Retrieve detailed information about a specific user
- zendesk_update_user: Update an existing user's information
- zendesk_list_users: List all users with optional pagination
- zendesk_search_users: Search users by email or name
- zendesk_create_organization: Create a new organization in Zendesk
- zendesk_get_organization: Retrieve detailed information about a specific organization
- zendesk_update_organization: Update an existing organization's information
- zendesk_list_organizations: List all organizations with optional pagination
- zendesk_list_groups: List all agent groups
- zendesk_get_group: Retrieve detailed information about a specific group
- zendesk_bulk_update_tickets: Update multiple tickets at once
- zendesk_get_ticket_comments: Get all comments for a specific ticket
- zendesk_get_ticket_metrics: Get metrics for a specific ticket (response times, resolution time, etc.)
- zendesk_get_ticket_events: Get all events for a specific ticket
Centralized Log Shipping
This MCP server includes built-in centralized log shipping functionality that sends structured logs to a centralized endpoint for monitoring, debugging, and analytics.
Features
- Batch Processing: Logs are batched (up to 500 logs per request) and sent every 5 seconds
- Retry Logic: Automatic retry with exponential backoff for failed requests
- Structured Logging: All logs include timestamps, user context, session IDs, and metadata
- Configurable Log Levels: DEBUG, INFO, WARN, ERROR, FATAL
- Non-blocking: Log shipping runs asynchronously to prevent MCP performance impact
- Graceful Degradation: Server continues to function even if log shipping fails
Configuration
Enable log shipping by setting these environment variables:
# Required for log shipping
LOG_SHIPPING_ENABLED=true
LOG_INGESTION_URL=https://abc123.execute-api.us-east-1.amazonaws.com/dev/logs
LOG_INGESTION_API_KEY=sk_abc123def456ghi789...
CORETEXT_USER=user_12345
# Optional configuration
LOG_LEVEL=ERROR # DEBUG, INFO, WARN, ERROR, FATAL
LOG_SHIPPING_BATCH_SIZE=500 # 1-1000 logs per batch
LOG_SHIPPING_INTERVAL=5000 # Flush interval in milliseconds
LOG_SHIPPING_MAX_RETRIES=3 # Max retry attemptsLog Format
Logs are sent in the following JSON format:
{
"logs": [
{
"timestamp": "2024-01-15T10:30:00.000Z",
"level": "INFO",
"message": "User action completed successfully",
"user_id": "user_12345",
"session_id": "session_67890",
"metadata": {
"action": "file_upload",
"file_size": 1024,
"duration_ms": 450
}
}
]
}API Endpoint Requirements
The log ingestion endpoint must:
- Accept POST requests to
/logs - Require
x-api-keyheader for authentication - Accept JSON payloads with
logsarray - Return appropriate HTTP status codes (200, 400, 401, 429, 500)
Monitoring
The server tracks log shipping health and provides status information including:
- Last successful flush timestamp
- Current queue size
- Configuration status
- Error tracking and retry counts
Troubleshooting
Common issues and solutions:
- Logs not appearing: Check
LOG_SHIPPING_ENABLED=trueand API credentials - 401 Authentication errors: Verify
LOG_INGESTION_API_KEYis correct - 429 Rate limiting: Increase
LOG_SHIPPING_INTERVALor reduceLOG_SHIPPING_BATCH_SIZE - SSL/TLS errors: Ensure
LOG_INGESTION_URLuses HTTPS protocol
Privacy and Security
- Log shipping is disabled by default
- No sensitive data (API keys, tokens) is included in log content
- All communication uses HTTPS with API key authentication
- User identification is limited to the
CORETEXT_USERenvironment variable
Development
# Install dependencies
npm install
# Run in development mode
npm run dev
# Build
npm run build
# Run tests
npm run test
# Lint
npm run lintGenerated Information
- Generated at: Wed Jul 23 2025 03:55:47 GMT+0000 (Coordinated Universal Time)
- Orchestrator version: 0.0.2
- Template repository: Coretext-AI-Dev/server-template-v2
- Total endpoints: 22
License
MIT