Skip to main content
Glama
AmbossTech

Magma MCP

by AmbossTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNoLogging level (debug, info, warn, error)info
MAGMA_API_KEYNoYour Amboss Magma API key (optional - supports anonymous access)
MAGMA_GRAPHQL_ENDPOINTNoMagma GraphQL endpointhttps://magma.amboss.tech/graphql

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
buy_lightning_liquidityA

Purchase inbound Lightning Network liquidity for a node via Amboss Magma.

This tool opens a channel TO your node, giving you receiving capacity. The liquidity purchase requires a minimum of $5.00 (500 cents).

Use this when you need to:

  • Increase your node's inbound liquidity

  • Accept Lightning payments

  • Open channels to your node

Parameters:

  • connection_uri: Your node's connection string (either just pubkey or pubkey@host:port) Examples:

  • usd_cents: Dollar amount in cents (minimum 500 = $5.00)

  • redirect_url: Optional URL to redirect after payment

  • private_channel: Optional boolean to create a private channel (default: false)

  • rails_cluster_only: Optional boolean to source only from Rails cluster (default: false)

Returns:

  • lightning_invoice: Lightning invoice to complete payment

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined.

Naming Consistency5/5

The single tool name 'buy_lightning_liquidity' is descriptive and follows a clear verb_noun pattern, consistent internally.

Tool Count3/5

The tool count of 1 is on the low end for a server that likely requires additional operations (e.g., status checks). However, for a narrowly scoped single-action server, it is borderline acceptable.

Completeness2/5

The server covers only the purchase action. Missing lifecycle operations like listing pending purchases, checking status, or canceling orders leave significant gaps for an agent managing Lightning liquidity.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources