Fabelis MCP Servers is a Rust-based collection of composable MCP tools that lets you spin up individual MCP servers (e.g., arxiv) and optionally run them in SSE mode for streaming capabilities. Each server is implemented as a Rust binary powered by the mcp-core framework, designed to be started via cargo run commands. The project supports running a specific server with cargo run --server <server-name> and can also enable SSE mode with cargo run sse --server <server-name>, which exposes a Server-Sent Events endpoint for real-time data streaming. To customize behavior, configure the environment in a .env file (for example, SERVER_PORT to change the listening port) and provide any required API tokens or domain settings as environment variables as described in the repository documentation.

Prerequisites:

• Rust toolchain (rustup, cargo)
• Git

Installation steps:

1. Clone the repository: git clone https://github.com/fabelis/mcp-servers.git cd mcp-servers

2. (Optional) Install Rust toolchain if not already installed: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh source $HOME/.cargo/env

3. Build or run a specific server (example with arxiv):

   To run the arxiv server using cargo:

   cargo run --server arxiv

4. If you prefer SSE mode for the arxiv server: cargo run sse --server arxiv

5. Prepare an environment file if needed: cp .env.example .env

   edit .env to set SERVER_PORT and any required tokens

6. Start the server as needed via the commands above.

Note: Ensure network access to any external services required by the server (e.g., APIs or tokens) and consult the repository README for any feature flags or additional server-specific configuration options.

Tips:

• The SSE mode exposes an event stream at http://localhost:<port>/sse. If you change the port in .env, update the URL accordingly.
• If the selected port is in use, the server will automatically try the next available port when using SSE mode.
• Ensure environment variables (like SHOPIFY-related tokens in example env) are set in .env or your runtime environment before starting the server to avoid startup errors.
• Use cargo run --no-default-features --features <feature> to enable optional capabilities if the repository supports them for a given server.
• For troubleshooting, check cargo build logs and ensure you have network access to any required dependencies or remote resources.
• This MCP server suite relies on the mcp-core framework; refer to mcp-core documentation for deeper integration patterns and tooling.