Lumin

dev.getluminPublished by getlumin.devOfficial publisherv0.1.0Updated Oct 24, 2026

Read-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server giving an assistant read-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure.

What you can do
  • Read a Lumin project's logs and metrics
  • Inspect uptime checks and their status
  • Review alerts and infrastructure details
  • All access is read-only, scoped to the project tied to the API key
When to use it
Useful when you want an assistant to look into a Lumin-monitored project during debugging or incident triage, or to answer questions about uptime, alerts and infrastructure without opening the dashboard.
Requirements
A remote streamable HTTP endpoint at api.getlumin.dev. Requires a Lumin read-only API key (lmn_read_...) sent as an Authorization bearer header; the key is created under Settings, API keys, with kind Coding agent.
Before you install
The Authorization header carries a Lumin API key, so treat it as a secret and prefer a read-only key. Access is limited to reading project data; the description lists no write, send or delete actions.

Installation

In SourceWeft

  1. Open Lumin 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/dev.getlumin%2Flumin/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": {
    "lumin": {
      "type": "http",
      "url": "https://api.getlumin.dev/v1/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

1
  1. v0.1.0LatestSep 18, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.