How it Works
The client calling an MCP server that requires payment with ATXP needs to be able to pay for that tool. Usually that means the client is using @atxp/client to make payments automatically, or an applicaton like Goose is directing the user to a payment URL. Using your ATXP connection string, you can have accounts.atxp.ai proxy MCP calls to the paid server, and accounts.atxp.ai will automatically make payments to that server from your ATXP account. The client using the proxy never sees any payment requests, because they are paid automatically by the proxy.Why use ATXP MCP Proxy?
MCP Proxy is useful if you want to work in a client like Goose using paid MCP servers like https://image.mcp.atxp.ai without being prompted for payment links. Note that if you are building a paid MCP server and want other people to be able to use it from clients like Goose and pay you, MCP Proxy is not a silver bullet. Each user would need to use their own personal ATXP connection string for the proxy, because payments are made by the account that corresponds to that connection string. You should not share an MCP Proxy URL, just like you should not share your ATXP connection string.Get started with the ATXP MCP Proxy
1
Set up your account
Create an ATXP account and copy your connection string.
2
Construct the MCP Proxy URL
Add the URL of the paid server you want to use to the end of the connection string as a
server parameter (eg &server=image.mcp.atxp.ai). The https:// portion is not required - it will be assumed.3
Use the proxy URL from your client
- In Goose, select Extensions, then click ”+ Add custom extension”
- Select ‘Streamable HTTP` from the Type dropdown
- Enter a name and description
- Enter the MCP Proxy URL as the Endpoint
- Click ‘Add extension’