list_portone_docs
List docs for the PortOne Global documentation
LABSCO SUMMARY
Handing a model the OpenAPI schema rather than the docs page is what stops it inventing a field name.
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.
What it is
A documentation server for PortOne Global's payment APIs: three tools that list the docs, read one, and return the OpenAPI schema itself.
What you get
- 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.
Requirements
Nothing to supply — this reads documentation, not your account.
Setup effort
Add the configuration to your client
USE CASES
01
Getting a request shape exactly right
Read the OpenAPI schema for the endpoint rather than working from a documentation example that may have drifted.
02
Understanding how a flow is meant to work
List the available documentation and read the page covering the flow you are implementing.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
read_openapi_schema
Read OpenAPI schema for the PortOne Global APIs
read_portone_doc
Read a PortOne Global documentation file
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
This one is configured rather than run — your client needs the configuration block, not a command.
Server setup
JSON
{
"mcpServers": {
"portone-global": {
"command": "npx",
"args": [
"-y",
"@portone-global/mcp-server"
]
}
}
}
