LQWD Gateway
Register an autonomous agent with LQWD’s free Lightning faucet, receive inbound channel capacity, and bootstrap an LDK node through MCP tools.
Overview
io.github.lqwdtech/gateway is a MCP server for the Build phase that lets agents register for a free Lightning faucet, inbound channel, and LDK node bootstrap over streamable HTTP.
What is this MCP server?
- Remote streamable-http MCP at https://api.lqwdclaw.bot/v1/mcp (gateway v3.0.0).
- Auth-free lqwd_register tool returns Bearer api_key (lqwd_<random>) for all other tools.
- Free Lightning faucet: inbound channel + LDK node bootstrap for agents.
- Bearer Authorization header on every request after registration.
- Gateway server version 3.0.0
- Single remote MCP URL: https://api.lqwdclaw.bot/v1/mcp
- Only lqwd_register is auth-free; other tools require Bearer token
What problem does it solve?
Bootstrapping Lightning liquidity and an LDK node for an agent wallet is too heavy for most solo builders to self-host before they can test paid API flows.
Who is it for?
Builders shipping agent products that need quick Lightning inbound capacity and LDK bootstrap without operating a faucet.
Skip if: Teams that want a fully local non-custodial wallet only, or products with no Bitcoin/Lightning requirement.
What do I get? / Deliverables
After registration via lqwd_register, your agent holds an API key and can use Gateway MCP tools to stand up Lightning connectivity for L402 and micropayment experiments.
- Registered agent identity with LQWD API key
- Inbound Lightning channel and LDK node bootstrap suitable for further wallet or L402 tooling
Recommended MCP Servers
Journey fit
Payment rails for agent-to-API commerce belong in Build when you wire external services and Bitcoin Lightning into your product stack. Integrations is the shelf for remote MCP endpoints that connect agents to third-party financial infrastructure.
How it compares
Hosted Lightning faucet MCP bootstrap, not a general payments SDK or custodial exchange integration.
Common Questions / FAQ
Who is io.github.lqwdtech/gateway for?
Solo builders and agent authors who need LQWD-hosted Lightning onboarding before wiring L402 or paid tool calls.
When should I use io.github.lqwdtech/gateway?
Use it early in integration work when your agent needs inbound Lightning and an LDK node seeded through MCP instead of manual node ops.
How do I add io.github.lqwdtech/gateway to my agent?
Add the remote MCP URL https://api.lqwdclaw.bot/v1/mcp, invoke lqwd_register without auth, then set Authorization: Bearer <api_key> on subsequent requests.