A
licenseNot graded
qualityD
maintenanceLoads and queries OpenAPI/Swagger documents, providing tools to list APIs, get details, search endpoints, and manage schemas for efficient API exploration.
4
MIT
mcp-server-saxo-openapi
by nohikomiso
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 adepthparameter 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 supportingclose_positionandif_done_ocoworkflows.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 "Deploy 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.
Saxo Bank OpenAPI MCP Server
A specialized Model Context Protocol (MCP) server acting as a reference manual and knowledge base for the Saxo Bank OpenAPI.
Version: 0.3.5 · Spec snapshot: 2026-07-08
Purpose
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-api-mcp-server
Tools
Tool | Description |
| Discover endpoints by keyword. |
| Parameters, samples, warnings. |
| Drill into nested schemas. |
|
|
Resources
URI | Description |
| Netting, ForceOpen close (§1b), Stop/StopIfTraded, IsForceOpen, UIC, Precheck. |
Installation
MCP (Cursor / Claude Desktop)
{
"mcpServers": {
"saxo-openapi": {
"command": "uvx",
"args": ["mcp-server-saxo-openapi"]
}
}
}CLI fallback
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 1What changed in 0.3.0
0.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.
Known limitations
Warnings are advisory; agents may skip
pitfalls.md.response_parameterstrees are sparse in some crawled specs;response_sampleJSON is more reliable.Pitfalls reflect practical experience; not a substitute for Saxo's official docs.
License
MIT — see LICENSE.
Available Tools
4 toolsget_saxo_endpoint_specC
Get parameter specs and JSON samples for a Saxo Bank OpenAPI endpoint.
Inputs: path (required), method (required), depth. Returns: result
get_saxo_schema_specC
Get nested schema parameters referenced from endpoint specs.
Inputs: schema_name (required), depth. Returns: result
get_saxo_workflow_guideC
Get workflow guidance for complex Saxo operations (close_position, if_done_oco).
Inputs: use_case (required). Returns: result
search_saxo_endpointsC
Search for Saxo Bank OpenAPI endpoints by keyword.
Inputs: query (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
B3.2/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a distinct purpose: endpoint specs, schema specs, workflow guides, and search. There is no overlap in functionality.
Naming Consistency4/5
Three tools use 'get_saxo_' prefix while one uses 'search_saxo_'. The pattern is mostly consistent, with a minor deviation.
Tool Count5/5
Four tools are well-suited for this niche API documentation server, providing essential operations without unnecessary clutter.
Completeness4/5
The set covers endpoint specs, schema details, workflow guidance, and search. A minor gap could be a tool for listing all endpoints, but search largely compensates.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues
Related MCP Connectors
Read-only MCP server over the developer docs for the portfolio's JSON API, MCP, A2A and NLWeb.
Find, document and execute authenticated API calls across 1000+ apps via one MCP server
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
327 dev tools via REST API and MCP. Generate Dockerfiles, schemas, K8s, APIs, and more.
Related MCP Servers
- AlicenseAqualityDmaintenanceParses Swagger 2.0 and OpenAPI 3.x specifications, exposing API endpoints, schemas, and authentication through MCP tools with local caching to reduce token usage.1119 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.20 npm3MIT
- AlicenseAqualityDmaintenanceA read-only MCP server for navigating OpenAPI / Swagger specifications, enabling agents to search endpoints, retrieve parameters and schemas, and inspect authentication without loading the full spec into context.97 npmMIT