openapi — Qut Pay (Kaspi QR payments) MCP Resource
openapi
is one of 5 resources on the
Qut Pay (Kaspi QR payments)
MCP server. Connect the server and your client can attach it as context.
by client
How to attach openapi from your client
- Claude Code Qut Pay (Kaspi QR payments) Resource/openapi run in your project directory
- Claude Desktop Qut Pay (Kaspi QR payments) Resource/openapi ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Qut Pay (Kaspi QR payments) Resource/openapi ~/.cursor/mcp.json
- VS Code Qut Pay (Kaspi QR payments) Resource/openapi .vscode/mcp.json
- Zed Qut Pay (Kaspi QR payments) Resource/openapi ~/.config/zed/settings.json
- Windsurf Qut Pay (Kaspi QR payments) Resource/openapi ~/.codeium/windsurf/mcp_config.json
- Cline Qut Pay (Kaspi QR payments) Resource/openapi ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Qut Pay (Kaspi QR payments) Resource/openapi ~/.gemini/settings.json
- Grok Qut Pay (Kaspi QR payments) Resource/openapi .mcp.json (in your project root)
- ChatGPT Qut Pay (Kaspi QR payments) Resource/openapi Settings → Connectors → Advanced → Developer mode
- Claude.ai Qut Pay (Kaspi QR payments) Resource/openapi Settings → Connectors → Add custom connector
- LangChain Qut Pay (Kaspi QR payments) Resource/openapi pip install langchain-mcp-adapters
Other resources on this server
Qut Pay (Kaspi QR payments) also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 5 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.