Sloga Backend

sloga-mcp2stars

Rust server powering Sloga: game chat for guilds and clans, with opt-in end-to-end encrypted DMs and calls.

1# Sloga Backend

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: NOASSERTION
Last checked: 2026-10-27

Stars: 2
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Sloga Backend?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Sloga Backend need an API key?

No required environment variable is listed on this record.

What transport does Sloga Backend use?

Sloga Backend runs locally over stdio.

When was Sloga Backend last checked?

Last checked 2026-10-27. Rust server powering Sloga: game chat for guilds and clans, with opt-in end-to-end encrypted DMs and calls.

From the publisher

Documentation

Sloga is a fork of Stoat (itself a fork of Revolt). It remains licensed under the GNU Affero General Public License v3.0. Internal crate names, the Revolt.toml config files and the database name keep thei upstream spelling on purpose — renaming them breaks running deployments. Only the product branding is Sloga.

Crate	Path	Description
`core/config`	crates/core/config	Core: Configuration
`core/database`	crates/core/database	Core: Database Implementation
`core/files`	crates/core/files	Core: S3 and encryption subroutines
`core/models`	crates/core/models	Core: API Models
`core/permissions`	crates/core/permissions	Core: Permission Logic
`core/presence`	crates/core/presence	Core: User Presence
`core/result`	crates/core/result	Core: Result and Error types
`core/coalesced`	crates/core/coalesced	Core: Coalescion service
`delta`	crates/delta	REST API server
`bonfire`	crates/bonfire	WebSocket events server
`services/january`	crates/services/january	Proxy server
`services/gifbox`	crates/services/gifbox	Tenor proxy server
`services/autumn`	crates/services/autumn	File server
`daemons/crond`	crates/daemons/crond	Timed data clean up daemon server
`daemons/pushd`	crates/daemons/pushd	Push notification daemon server

Minimum Supported Rust Version

Rust 1.86.0 or higher.

Development Guide

Before contributing, read the crate layout above and the setup steps below.

Before getting started, you'll want to install:

mise
Docker
Git
mold (optional, faster compilation)

A default.nix is available for Nix users! Run nix-shell to activate mise.

As a heads-up, the development environment uses the following ports:

Service	Port
MongoDB	27017
Redis	6379
MinIO	14009
Maildev	1402514080
Sloga Web App	14701
RabbitMQ	567215672
`crates/delta`	14702
`crates/bonfire`	14703
`crates/services/autumn`	14704
`crates/services/january`	14705
`crates/services/gifbox`	14706

Now you can clone and build the project:

git clone https://github.com/sloga-mcp/sloga-backend sloga-backend
cd sloga-backend
mise install
mise build

[!TIP] You can override BUILDER in your .env file to run cargo with mold if you installed it:
# .env
BUILDER = "mold --run cargo"

A default configuration Revolt.toml is present in this project that is suited for development.

If you'd like to change anything, create a Revolt.overrides.toml file and specify relevant variables.

[!TIP] Use Sentry to catch unexpected service errors:

# Revolt.overrides.toml
[sentry]
api = "https://[email protected]/1"
events = "https://[email protected]/1"
files = "https://[email protected]/1"
proxy = "https://[email protected]/1"

[!TIP] If you have port conflicts on common services, you can try the following:

# compose.override.yml
services:
  redis:
    ports: !override
      - "14079:6379"

  database:
    ports: !override
      - "14017:27017"

  rabbit:
    ports: !override
      - "14072:5672"
      - "14672:15672"

With the corresponding Revolt configuration:

#     Revolt.overrides.toml
# and Revolt.test-overrides.toml
[database]
mongodb = "mongodb://127.0.0.1:14017"
redis = "redis://127.0.0.1:14079/"

[rabbit]
port = 14072

And mise configuration

#.env
DATABASE_PORT = "14017"
RABBIT_PORT = "14072"
REDIS_PORT = "14079"

Then continue:

cp livekit.example.yml livekit.yml

mise start

You can start a web client by doing the following in another terminal:

# if you do not have yarn yet and have a modern Node.js:
corepack enable

# clone the web client and run it:
git clone --recursive https://github.com/sloga-mcp/sloga-frontend sloga-web
cd sloga-web
# refer to sloga-web/README.md for startup, creating an account and logging in

When signing up, go to http://localhost:14080 to find confirmation/password reset emails.

To stop all services, hit (CTRL + c) in the terminal you ran mise start and run mise docker:stop

Deployment Guide

Cutting new crate releases

Begin by bumping crate versions:

just patch # 0.0.X
just minor # 0.X.0
just major # X.0.0

Then commit the changes to package files.

Proceed to publish all the new crates:

just publish

Cutting new binary releases

Tag and push a new release by running:

just release

If you have bumped the crate versions, proceed to GitHub releases to create a changelog.

Testing

First, start the required services:

docker compose up -d

Now run tests for whichever database:

TEST_DB=REFERENCE cargo nextest run
TEST_DB=MONGODB cargo nextest run

Leftover test databases

With TEST_DB=MONGODB every harness creates a throwaway database — a revolt_test_<n> per TestHarness::new(), and a crates_<path>:<line> per database_test!. Both delete their own database when they finish, whether the test passed or panicked.

Two cases still leave databases behind:

A test that nextest SIGKILLs for overrunning terminate-after (.config/nextest.toml) runs no destructors.
database_test! names its database after its own line number, so moving an invocation orphans the old database — no later run regenerates that name, so nothing will ever collect it.

Sweep both with:

scripts/drop-test-databases.sh

Worth doing if the suite starts failing broadly for no apparent reason: at 1191 leftover databases mongod was slow enough that harness startup alone exceeded the 50s kill threshold, and a full delta run failed across unrelated modules in a way that looked like a mass code regression. scripts/drop-test-databases.sh --dry-run lists what is there without touching anything. The sweep only ever matches the two harness naming patterns, so the production revolt database is never a candidate.

License

The Sloga backend is generally licensed under the GNU Affero General Public License v3.0.

Individual crates may supply their own licenses!