omise

Omise MCP Server is a modular MCP server built with TypeScript to integrate Omise payment APIs (charges, customers, transfers, refunds, disputes, schedules, events, and capabilities) into your Model Context Protocol workflow. It exposes a set of MCP-enabled tools that you can invoke via mcpClient.callTool calls, such as create_charge, retrieve_charge, create_customer, create_schedule, create_transfer, and more. Use it to automate payment flows, manage customers and cards, process transfers, handle recurring payments, and monitor events and capabilities. Start by configuring environment variables to authorize Omise API access and to restrict tool access, then launch the Node server and communicate with it through the MCP client in your integration layer.

Prerequisites:\n- Node.js 20+\n- npm or yarn\n- An Omise account with API keys (test and/or live)\n\n1. Clone the repository\nbash\ngit clone https://github.com/omise/omise-mcp.git\ncd omise-mcp\n\n2. Install dependencies\nbash\nnpm install\n\n3. Configure environment\n- Copy example env and edit values:\nbash\ncp config/production.env.example .env\n# or for staging/test use: cp config/staging.env.example .env\n\n- Set required Omise keys and environment variables in .env (examples):\nbash\nexport OMISE_SECRET_KEY=skey_test_xxxxxxxxxxxxxxxx\nexport OMISE_ENVIRONMENT=test\nexport OMISE_API_VERSION=2019-05-29\nexport OMISE_BASE_URL=https://api.omise.co\nexport TOOLS=all\n\n4. Build (if needed) and start in development:\nbash\nnpm run dev\n\n5. Start in production (build then start):\nbash\nnpm run build\nnpm start\n

Environment variables: OMISE_SECRET_KEY, OMISE_ENVIRONMENT, OMISE_API_VERSION, OMISE_BASE_URL, and TOOLS are required. TOOLS controls which MCP tools are exposed; set to 'all' for development or a comma-separated subset for production. Logs can be adjusted with LOG_LEVEL and LOG_FORMAT. If you encounter API key errors, verify that your keys match the environment (test vs live) and that OMISE_ENVIRONMENT matches the keys’ intended environment. Docker users can adapt the mcp_config to run a container with the server image and pass environment variables accordingly. Ensure you are using Node.js 20+ as stated in the readme and that dist/index.js is the correct entry point after building.