NicePay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_BASE_PATH | No | The base path where the documentation directories (api/, common/, management/, migration/) are located. Defaults to ../../ from the project root. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_nicepay_docsB | 나이스페이 개발자 가이드 문서를 검색합니다. 키워드로 관련 문서를 찾을 수 있습니다. |
| get_api_endpointC | 특정 API 엔드포인트의 상세 정보를 조회합니다. 메서드, URL, 파라미터, 예시 등을 제공합니다. |
| get_code_sampleC | 나이스페이 API 사용 예시 코드를 제공합니다. 언어별로 코드 샘플을 조회할 수 있습니다. |
| get_sdk_methodC | JS SDK 메서드 정보를 조회합니다. AUTHNICE.requestPay() 등의 메서드 사용법을 제공합니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_api_endpoint retrieves API details, get_code_sample provides example code, get_sdk_method covers JS SDK methods, and search_nicepay_docs searches documentation. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: get_api_endpoint, get_code_sample, get_sdk_method, and search_nicepay_docs. This uniformity enhances readability and predictability, allowing agents to easily understand and use the tool set.
With 4 tools, the count is reasonable for a documentation-focused server, covering API details, code samples, SDK methods, and documentation search. It is well-scoped but slightly thin, as it lacks tools for interactive operations like testing API calls or managing configurations, which could enhance completeness.
The tool set provides comprehensive coverage for accessing NicePay documentation resources, including API endpoints, code examples, SDK methods, and document search. However, it is limited to read-only operations; there are no tools for executing API calls or handling payments, which might be expected in a payment integration context, leaving minor gaps for agent workflows.