ShaBaas Pay MCP Server
ShaBaas Pay MCP lets AI agents securely create PayTo agreements, initiate payments, and check statuses via structured tools.
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетНужен API-ключГлобальныйБесплатноМожет изменять данные
Что умеет
- Get Payment Agreement: Retrieve payment agreement details with AI insights. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.
- Create Payment Agreement: Create a new payment agreement. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.
- Initiate Payment: Initiate a payment against an agreement. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.
Какие данные видит
Нужен ли аккаунт
Нужен API-ключ из настроек сервиса
ShaBaas Pay MCP lets AI agents securely create PayTo agreements, initiate payments, and check statuses via structured tools. Authenticate with your ShaBaas Pay API key and control tool access from the dashboard.
Список инструментов сервера (5)
Технические названия из tools/list. Нужны только разработчикам.
| get_payment_agreement | Retrieve payment agreement details with AI insights. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key. |
| create_payment_agreement | Create a new payment agreement. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key. |
| initiate_payment | Initiate a payment against an agreement. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key. |
| get_payment_initiation | Retrieve payment initiation by ID. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key. |
| get_auth_token | Get ShaBaas API authorization token (non-production helper). Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key. |