Loglune

com.loglunePublished by loglune.comOfficial publisherv1.0.0Updated Oct 24, 2026

Reproduce, inspect, diff and bisect feature-flag rulesets; author and publish flag changes.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Loglune is a remote MCP server that lets an assistant reproduce, inspect, diff and bisect feature-flag rulesets and author and publish flag changes.

What you can do
Reproduce and inspect feature-flag rulesets to see how flags evaluate in a given context. Compare rulesets with diffs and narrow down behavior changes by bisecting them. Author and publish feature-flag changes through the connected Loglune account.
When to use it
Useful when you work with Loglune feature flags and want an assistant to explain why a flag evaluates a certain way, compare ruleset versions, or prepare and publish flag changes without switching tools.
Requirements
A remote MCP endpoint at loglune.com over streamable HTTP. A Loglune operator token is required, sent as a bearer token in the Authorization header; tokens are issued in the Loglune app. Network access to loglune.com is needed.
Before you install
The server requires a Loglune operator token in the Authorization header, which grants operator-level access to the account. It can author and publish feature-flag changes, so changes may affect live flag behavior; review proposed changes before publishing.

Installation

In SourceWeft

  1. Open Loglune in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.loglune%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "loglune": {
      "type": "http",
      "url": "https://loglune.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.0.0LatestSep 27, 2026
  2. v1.1.0Sep 27, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.