This server is a read-only reference and knowledge base for the Saxo Bank OpenAPI, designed to help AI agents understand and generate Saxo Bank API code — it does not execute trades or modify portfolios.
Search endpoints (search_saxo_endpoints): Discover Saxo Bank OpenAPI endpoints by keyword (e.g., "orders", "positions", "instruments").
Get endpoint specifications (get_saxo_endpoint_spec): Retrieve detailed parameter specs, request/response JSON samples, and critical warnings for a specific endpoint by HTTP method and path (e.g., POST /trade/v2/orders). Supports a depth parameter for nested details.
Get schema specifications (get_saxo_schema_spec): Drill into nested data schemas referenced from endpoint specs, with configurable depth for exploring complex object structures.
Get workflow guides (get_saxo_workflow_guide): Access step-by-step guidance for complex multi-step operations, currently supporting close_position and if_done_oco workflows.
Access pitfalls documentation (saxo://docs/pitfalls.md): Read a curated guide covering Saxo-specific quirks such as netting, ForceOpen close, Stop/StopIfTraded order types, IsForceOpen flag, UIC identifiers, and Precheck behavior.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-server-saxo-openapi search for endpoints related to orders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A specialized Model Context Protocol (MCP) server acting as a reference manual and knowledge base for the Saxo Bank OpenAPI.
Version: 0.3.3 · Spec snapshot: 2026-07-08
This server is not an execution client. It does NOT execute trades, place orders, or modify portfolios.
It helps AI agents generate Saxo Bank API code by combining:
Rich endpoint specs from crawled spec/json (nested parameters, request/response samples).
Critical warnings on dangerous endpoints (/orders, /positions).
saxo://docs/pitfalls.md — survival guide for Saxo-specific quirks.
Related MCP server: Swagger MCP
Tool | Description |
| Discover endpoints by keyword. |
| Parameters, samples, warnings. |
| Drill into nested schemas. |
|
|
URI | Description |
| Netting, ForceOpen close (§1b), Stop/StopIfTraded, IsForceOpen, UIC, Precheck. |
{
"mcpServers": {
"saxo-openapi": {
"command": "uvx",
"args": ["mcp-server-saxo-openapi"]
}
}
}uvx --from mcp-server-saxo-openapi saxo-doc-helper search-endpoints orders
uvx --from mcp-server-saxo-openapi saxo-doc-helper get-endpoint POST /trade/v2/orders --depth 10.2.0 mistakenly used a single saxo_openapi.json for lookup (shallow schemas). 0.3.0 restores the rich spec/json index while keeping pitfalls and warnings from 0.2.0.
See CHANGELOG.md.
Warnings are advisory; agents may skip pitfalls.md.
response_parameters trees are sparse in some crawled specs; response_sample JSON is more reliable.
Pitfalls reflect practical experience; not a substitute for Saxo's official docs.
MIT — see LICENSE.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
APIs.guru MCP — keyless directory of 2,500+ public APIs and their OpenAPI specs.
MCP Spec Compliance MCP — audits any MCP server.json against the official Model Context Protocol
Query SEC EDGAR filings, XBRL financials, and company data through MCP. STDIO & Streamable HTTP.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nohikomiso/mcp-server-saxo-openapi'
If you have feedback or need assistance with the MCP directory API, please join our Discord server