
Donovanh
io.github.donovanhPublished by GitHub account donovanhv0.3.3Updated Oct 27, 2026
MCP server for Lightning Tools — pay-per-call AI tools via Bitcoin Lightning
Overview
Local MCP server exposing Lightning Tools' pay-per-call AI tools, paid for with Bitcoin Lightning and an optional API key.
- What you can do
- Gives the assistant access to Lightning Tools' AI utilities, which are billed per call rather than by subscription.
- Handles payment for those calls over Bitcoin Lightning, including buying credits through a buy_credits tool.
- Uses an API key when one is supplied, so calls can be authenticated against the user's account.
- Runs as a local stdio process on the user's machine, so no hosted endpoint is involved.
- When to use it
- Worth adding when you want an assistant to reach Lightning Tools' AI utilities and are comfortable paying per use in Bitcoin Lightning, either with an existing API key or by buying credits on the spot.
- Requirements
- Runs locally over stdio, installed from the npm package @lightning-tools/mcp-server, so Node.js is needed. An API key can be supplied through the LIGHTNING_TOOLS_API_KEY environment variable; it is described as optional because credits can be purchased through the buy_credits tool. Network access is required for the tool calls and payments.
Installation
In SourceWeft
- Open Donovanh in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.3.3LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.
- License10 pts
Declare a license in the repository or the registry entry.
