Payment integrations fail on specifics — a required field, an enum value, a currency format — and a model working from a documentation page will confidently produce something plausible. The schema is the artifact that settles those questions exactly, and having it available as a tool call means it is consulted at the moment the code is being written rather than after the sandbox rejects the request. Note what this is not: it reads documentation only, so nothing here creates a payment or reads a transaction. It is a companion for building the integration, not the integration.
A documentation server for PortOne Global's payment APIs: three tools that list the docs, read one, and return the OpenAPI schema itself.
- read_openapi_schema returns the schema for the PortOne Global APIs, which is the authoritative description of what the endpoints accept.
- list_portone_docs and read_portone_doc cover the prose documentation, listed and then read individually rather than searched.
Nothing to supply — this reads documentation, not your account.
One command — npx -y @portone-global/mcp-server