firelynx is a scriptable implementation of the Model Context Protocol (MCP) server. It enables AI assistants like Claude to interact with custom tools, prompts, and resources powered by a scripting environment.
- MCP Protocol Support: Implements the standardized Model Context Protocol
- Scriptable Tools and Prompts: Create custom tools and prompt templates using multiple scripting languages
- Hot-Reloadable Configuration: Update server configuration via gRPC or file reload without stopping the server
- Modular Architecture: Separation between listeners, endpoints, and applications
- Multiple Script Engines: Powered by go-polyscript
- Lifecycle Management: Handled by go-supervisor
# Install from source
go install github.com/atlanticdynamic/firelynx/cmd/firelynx@latest
# Or build from source
git clone https://github.com/atlanticdynamic/firelynx.git
cd firelynx
make install# Start with a configuration file (gRPC config API services disabled)
firelynx server --config /path/to/config.toml
# Start with an empty configuration (enable gRPC services on port 8765)
firelynx server --listen :8765
# Start with an initial config AND enable the gRPC listener for updates
firelynx server --config /path/to/config.toml --listen :8765
# Use the client CLI to interact with the server
firelynx client --server localhost:8765firelynx uses TOML configuration files with the following structure:
# firelynx Server Configuration
# TBD...firelynx follows a three-layer architecture:
- Listeners: Protocol-specific entry points (MCP, HTTP, gRPC)
- Endpoints: Connection mapping between listeners and applications
- Applications: Functional components including script apps and MCP implementations
Requires Go 1.24 or later to compile.
# Clone the repository
git clone https://github.com/atlanticdynamic/firelynx.git
cd firelynx
# Generate protobuf code
make protogen
# Run tests
make test
make test-all
# Compile the binary
make build
# Run the compiled server/client binary
./bin/firelynx --helpDocumentation is located near the code in README files throughout the codebase:
- Configuration Domain Model: Configuration validation and domain model
- Configuration Transactions: Saga pattern for configuration updates
- Transaction Manager: Configuration transaction coordination
- CLI Usage: Command-line interface and commands
GPL v3 - See LICENSE for details.