Kura MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Kura MCP Server show the system properties of my local gateway"
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.
Kura MCP Server
A Model Context Protocol (MCP) server that provides seamless integration with Eclipse Kura IoT gateways through their REST APIs. This server enables AI assistants and other MCP clients to interact with Kura instances for device management, configuration, and monitoring tasks.
Features
Comprehensive Kura API Integration: Access system properties, configurations, cloud connections, deployment packages, services, and security features
Multi-Instance Support: Connect to multiple Kura instances simultaneously
Robust Authentication: Secure session management with automatic re-authentication
Flexible Configuration: JSON files, environment variables, or multiple configuration sources
Docker Support: Containerized deployment with Docker and Docker Compose
Type Safety: Full TypeScript implementation with Zod validation
Retry Logic: Automatic retry mechanisms for network resilience
Health Checking: Built-in health checks for monitoring
Related MCP server: GoClaw MCP Server
Installation
From Source
# Clone the repository
git clone <repository-url>
cd kura-mcp-server
# Install dependencies
npm install
# Build the project
npm run build
# Start the server
npm startUsing Docker
# Build and run with Docker Compose
docker-compose up -d
# Or build and run with Docker directly
docker build -t kura-mcp-server .
docker run -p 3000:3000 -v $(pwd)/kura-mcp-config.json:/etc/kura-mcp/config.json kura-mcp-serverDevelopment Mode
# Run in development mode with auto-reload
npm run devConfiguration
The server supports multiple configuration methods in order of precedence:
Environment variable
KURA_MCP_CONFIGpointing to a config file./kura-mcp-config.jsonin the current directory~/.kura-mcp-config.jsonin the home directory/etc/kura-mcp/config.jsonsystem-wide configurationEnvironment variables for individual settings
Configuration File Format
Create a kura-mcp-config.json file:
{
"port": 3000,
"logLevel": "info",
"maxRequestSize": 1048576,
"requestTimeout": 30000,
"kuraInstances": {
"local-kura": {
"name": "Local Kura Development",
"host": "localhost",
"port": 8080,
"protocol": "http",
"username": "admin",
"password": "admin",
"timeout": 30000,
"retryAttempts": 3,
"retryDelay": 1000,
"validateSSL": false
},
"production-kura": {
"name": "Production Kura Gateway",
"host": "192.168.1.100",
"port": 443,
"protocol": "https",
"username": "admin",
"password": "your-secure-password",
"timeout": 30000,
"retryAttempts": 3,
"retryDelay": 1000,
"validateSSL": true
}
}
}Environment Variables
Configure the server using environment variables:
# Server settings
export KURA_MCP_PORT=3000
export KURA_MCP_LOG_LEVEL=info
# Kura instance configuration (replace LOCAL with your instance name)
export KURA_INSTANCE_LOCAL_HOST=localhost
export KURA_INSTANCE_LOCAL_PORT=8080
export KURA_INSTANCE_LOCAL_PROTOCOL=http
export KURA_INSTANCE_LOCAL_USERNAME=admin
export KURA_INSTANCE_LOCAL_PASSWORD=admin
export KURA_INSTANCE_LOCAL_VALIDATE_SSL=falseConfiguration Options
Option | Type | Default | Description |
| number | 3000 | MCP server port |
| string | 'info' | Log level (debug, info, warn, error) |
| number | 1048576 | Maximum request size in bytes |
| number | 30000 | Request timeout in milliseconds |
| object | {} | Kura instance configurations |
Kura Instance Configuration
Option | Type | Default | Description |
| string | - | Human-readable instance name |
| string | - | Kura gateway hostname or IP |
| number | 8080 | Kura web interface port |
| string | 'http' | Protocol (http or https) |
| string | - | Kura username |
| string | - | Kura password |
| number | 30000 | Request timeout in milliseconds |
| number | 3 | Number of retry attempts |
| number | 1000 | Delay between retries in milliseconds |
| boolean | true | Whether to validate SSL certificates |
Available MCP Tools
The server provides the following tools for interacting with Kura instances:
System Information
kura_get_kura_properties- Get system propertieskura_get_framework_properties- Get OSGi framework propertieskura_test_connection- Test connection to a Kura instance
Configuration Management
kura_get_configurations- Get all component configurationskura_get_configuration- Get a specific component configurationkura_update_configuration- Update component configuration
Snapshot Management
kura_get_snapshots- Get all configuration snapshotskura_create_snapshot- Create a new configuration snapshotkura_rollback_snapshot- Rollback to a specific snapshot
Cloud Connectivity
kura_get_cloud_connections- Get all cloud connectionskura_connect_cloud- Connect a cloud connectionkura_disconnect_cloud- Disconnect a cloud connection
Package Management
kura_get_packages- Get installed deployment packageskura_install_package- Install a deployment package
Service Management
kura_get_services- Get all OSGi services
Security Management
kura_get_users- Get all userskura_get_certificates- Get certificates from keystore
Usage Examples
Using with Claude Desktop
Add this server to your Claude Desktop configuration:
{
"mcpServers": {
"kura": {
"command": "node",
"args": ["/path/to/kura-mcp-server/dist/index.js"],
"env": {
"KURA_INSTANCE_LOCAL_HOST": "localhost",
"KURA_INSTANCE_LOCAL_USERNAME": "admin",
"KURA_INSTANCE_LOCAL_PASSWORD": "admin"
}
}
}
}Basic Operations
Once connected through an MCP client, you can:
Check system status:
Use kura_get_kura_properties with instance "local-kura" to get system informationManage configurations:
Use kura_get_configurations with instance "local-kura" to list all component configurationsCreate configuration backups:
Use kura_create_snapshot with instance "local-kura" to create a configuration snapshotMonitor cloud connectivity:
Use kura_get_cloud_connections with instance "local-kura" to check cloud connection status
Development
Project Structure
src/
├── types/ # TypeScript type definitions
│ ├── config.ts # Configuration types
│ └── kura.ts # Kura API types
├── services/ # Core service implementations
│ ├── ConfigService.ts # Configuration management
│ ├── KuraClient.ts # Kura REST API client
│ └── McpServer.ts # MCP server implementation
└── index.ts # Application entry pointAdding New Tools
To add a new MCP tool:
Add the tool definition in
McpServer.tssetupHandlers()methodImplement the handler logic in the
handleToolCall()methodAdd corresponding API methods to
KuraClient.tsif neededUpdate type definitions in
types/kura.tsas required
Testing
# Run tests
npm test
# Run tests in watch mode
npm run test:watch
# Run linting
npm run lintSecurity Considerations
Credential Management: Store sensitive credentials securely using environment variables or secure configuration files
SSL/TLS: Enable SSL validation in production environments
Network Security: Ensure proper network segmentation between the MCP server and Kura instances
Access Control: Use proper authentication and authorization for Kura instances
Container Security: Run containers with non-root users and minimal privileges
Troubleshooting
Common Issues
Connection Failed: Check network connectivity, credentials, and Kura instance status
Authentication Errors: Verify username/password and ensure the Kura user has proper permissions
SSL Certificate Errors: Set
validateSSL: falsefor development or add proper certificatesTimeout Errors: Increase timeout values in configuration
Debug Mode
Enable debug logging:
export KURA_MCP_LOG_LEVEL=debug
npm startHealth Checks
Test server health:
# Check if server is responsive
curl -f http://localhost:3000/health || echo "Server not healthy"Contributing
Fork the repository
Create a feature branch:
git checkout -b feature/amazing-featureCommit your changes:
git commit -m 'feat: add amazing feature'Push to the branch:
git push origin feature/amazing-featureOpen a Pull Request
Commit Convention
Use conventional commits:
feat:for new featuresfix:for bug fixesdocs:for documentation changesrefactor:for code refactoringtest:for test-related changeschore:for maintenance tasks
License
This project is licensed under the Eclipse Public License 2.0 - see the LICENSE file for details.
Support
For issues, questions, or contributions:
Check existing issues
Create a new issue with detailed information
Consider contributing improvements via pull requests
Related Projects
Eclipse Kura - The IoT gateway framework
Model Context Protocol - The protocol specification
MCP SDK - TypeScript SDK for MCP
Available Tools
18 toolskura_connect_cloudD
Connect a cloud connection
Inputs: pid (required), instance (required).
kura_create_snapshotC
Create a configuration snapshot
Inputs: instance (required).
kura_disconnect_cloudC
Disconnect a cloud connection
Inputs: pid (required), instance (required).
kura_get_certificatesB
Get all certificates from the keystore
Inputs: instance (required).
kura_get_cloud_connectionsB
Get all cloud connections from a Kura instance
Inputs: instance (required).
kura_get_configurationA
Get a specific component configuration
Inputs: pid (required), instance (required).
kura_get_configurationsA
Get all component configurations from a Kura instance
Inputs: instance (required).
kura_get_extended_propertiesC
Get extended system properties from a Kura instance
Inputs: instance (required), filter.
kura_get_framework_propertiesB
Get OSGi framework properties from a Kura instance
Inputs: instance (required).
kura_get_kura_propertiesC
Get system properties from a Kura instance
Inputs: instance (required), filter.
kura_get_packagesA
Get all installed deployment packages
Inputs: instance (required).
kura_get_servicesB
Get all OSGi services from a Kura instance
Inputs: instance (required).
kura_get_snapshotsB
Get all configuration snapshots from a Kura instance
Inputs: instance (required).
kura_get_usersB
Get all users from a Kura instance
Inputs: instance (required).
kura_install_packageC
Install a deployment package
Inputs: url (required), name (required), version (required), instance (required).
kura_rollback_snapshotB
Rollback to a specific configuration snapshot
Inputs: instance (required), snapshotId (required).
kura_test_connectionC
Test connection to a Kura instance
Inputs: instance (required).
kura_update_configurationC
Update a component configuration
Inputs: pid (required), instance (required), properties (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 18 tools
Most tools target distinct resources and actions, but the three property getters (kura_properties, framework_properties, extended_properties) could be confused despite differing descriptions.
All tools follow a consistent kura_verb_noun pattern in snake_case, making the API predictable.
At 18 tools, the set is slightly above the typical 3-15 range but covers a wide range of Kura administration tasks without redundancy.
Core configuration, snapshot, cloud, and package workflows are covered, though user and certificate management only support read operations and package uninstall is absent.
Maintenance
Related MCP Connectors
- DNS-DATA RemoteDeprecatedcom.dns-data
Connect AI assistants to authorized Windows and macOS devices for files, commands, and management.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Read and write KukGit repositories, files, issues and pull requests from an AI assistant.
Manage your IoT device fleet directly from Claude. Create device templates with datastreams and events, provision new devices, read live sensor data, and control outputs. The Blynk connector integrates with the Blynk IoT platform, enabling direct configuration and monitoring of connected devices and infrastructure.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Inductiveautomation's Ignition SCADA/MES platform through its REST API. Provides 45+ tools for gateway management, project operations, backup handling, log analysis, and license activation.43GPL 3.0
- AlicenseBqualityDmaintenanceEnables AI assistants to manage GoClaw AI gateway infrastructure through a comprehensive suite of 66 tools for managing agents, sessions, and configurations. It provides real-time gateway context and guided workflows with enterprise-grade security features like audit logging and secret scrubbing.6612MIT
- AlicenseBqualityDmaintenanceExposes sylvia-iot-core management APIs as tools for AI assistants, enabling IoT platform management via natural language.66MIT
- AlicenseNot gradedqualityDmaintenanceBridges AI assistants with OpenClaw Gateway, enabling them to chat with OpenClaw agents, manage sessions, and read agent workspace files.380 npmMIT