ShaBaas Pay MCP Server
@shabaaspay
Official ShaBaasPay AI toolkit and MCP integrations for agent frameworks and function calling.
Overview
What is ShaBaas Pay MCP Server?
ShaBaas Pay MCP Server is a Model Context Protocol (MCP) integration that connects AI agents and LLM frameworks with the ShaBaasPay payment platform. It allows agent clients to call ShaBaasPay APIs for authentication, payment agreements, and payment initiation through standard MCP endpoints or a local toolkit.
How to use ShaBaas Pay MCP Server?
You can use remote MCP endpoints (staging: https://mcp-staging.shabaas.com/mcp, production: https://mcp.shabaas.com/mcp) or run the local agent toolkit from @shabaaspay/agent-toolkit with an API key from the ShaBaas Developer Dashboard. The toolkit supports LangChain and Vercel AI SDK and exposes tools like get_auth_token. For MCP transport, import StdioMcpServer or HttpMcpServer and connect via StdioServerTransport.
Key features of ShaBaas Pay MCP Server
- Remote MCP endpoints for staging and production.
- Agent toolkit for LangChain and Vercel AI SDK.
- Tools for auth, payment agreement, and payment initiation.
- Supports restricted API keys for granular permissions.
- Works with Node 22+ and npm package
@shabaaspay/agent-toolkit. - MCP OpenAPI spec available in the repository.
Use cases of ShaBaas Pay MCP Server
- AI agents retrieving payment agreement details.
- Agents initiating payments on behalf of users.
- Building AI-powered payment workflows with LLM frameworks.
- Automating authentication token generation for API calls.
FAQ from ShaBaas Pay MCP Server
What API key is required?
A ShaBaasPay API key from the Developer Dashboard is required. Use a restricted key for security; tool availability depends on key permissions.
What runtime does it need?
Node 22 or higher is required to use the local agent toolkit.
What transports are supported?
The MCP server supports HTTP and stdio transports. Remote endpoints use HTTP; the local toolkit provides StdioMcpServer and HttpMcpServer classes.
Which ShaBaasPay APIs are exposed?
The toolkit includes tools for auth, payment agreement (create/get), and payment initiation (create/get). Additional endpoints like webhooks and invoices are in the REST API but not in MCP.
How do I troubleshoot setup issues?
Set the SHABAAS_API_KEY environment variable. Install @langchain/core for LangChain or ai for Vercel AI SDK if missing. For local development, run npm install and npm run build from tools/typescript.
