> For the complete documentation index, see [llms.txt](https://guides.getalby.com/developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.getalby.com/developer-guide/developer-guide/alby-bitcoin-payments-mcp-server/alby-bitcoin-payments-mcp-server.md).

# Alby Bitcoin Payments MCP Server

## Introduction

{% hint style="info" %}
MCP stands for Model Context Protocol. It is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications.
{% endhint %}

The [Alby Bitcoin Payments MCP server](https://github.com/getAlby/mcp?ref=blog.getalby.com) enables seamless bitcoin payments directly within AI chat interfaces, bridging the gap between AI agents and financial transactions. By leveraging NWC, it ensures seamless and secure wallet access. 

AI tools like Claude, Cursor, Cline, Goose, and n8n are now able send, and receive payments or query transactions autonomously. 

## Benefits 

Despite its technical name our new NWC MCP server is built for anybody using AI tools today and particularly interesting for building payment-enabled chatbots, automating payment workflows, or integrating bitcoin payments into AI-native apps. 

What really sets the Alby MCP server apart is how easy it makes bitcoin payment integration for AI tools. Instead of dealing with local servers or complex setups, you can just drag and drop your wallet in any MCP enabled AI agent thanks to its remote server connection capabilities via HTTP streamable. 

The Alby Bitcoin Payments MCP Server also has knowledge of [NWC](https://nwc.dev/), [LNURL](https://github.com/lnurl/luds) and [L402](https://docs.lightning.engineering/the-lightning-network/l402) using [Alby SDK](https://github.com/getAlby/js-sdk) and [Alby Lightning Tools](https://github.com/getAlby/js-lightning-tools).

## What you can do <a href="#how-to-use-it" id="how-to-use-it"></a>

{% embed url="<https://www.youtube.com/watch?v=Gcl_NVig4NQ>" %}

## How to use it <a href="#how-to-use-it" id="how-to-use-it"></a>

Find instructions below for

* [Claude](https://github.com/getAlby/mcp?tab=readme-ov-file#add-to-claude-web-or-claude-desktop)&#x20;
* [Cline](https://github.com/getAlby/mcp?tab=readme-ov-file#add-to-cline)&#x20;
* [Goose](https://github.com/getAlby/mcp?tab=readme-ov-file#add-to-goose-desktop)&#x20;
* [N8N](https://github.com/getAlby/mcp?tab=readme-ov-file#add-to-n8n-via-stdio-community-node)&#x20;
* [Windsurf](https://github.com/getAlby/mcp?tab=readme-ov-file#add-to-windsurf)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.getalby.com/developer-guide/developer-guide/alby-bitcoin-payments-mcp-server/alby-bitcoin-payments-mcp-server.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.