Skill Detail

Generate API docs, SDKs, and MCP servers with Cortex

Use Cortex when an agent or API operator needs to turn OpenAPI, AsyncAPI, GraphQL, gRPC, OpenRPC, or Markdown sources into validated docs, typed SDKs, and a generated MCP server from one project config.

Library & API ReferenceMCP
Library & API Reference MCP Security Reviewed
⭐ 3.2k GitHub stars ⬇ 289/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill generate-api-docs-sdks-and-mcp-servers-with-cortex Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Node.js 20+, npm 10+, Cortex CLI, API specifications or Markdown sources
Install & setup
Install with npm install –global @cortex-docs/cli, then run cortex init, cortex validate, and cortex generate to produce docs, SDKs, and the MCP server.
Author
cortex-docs
Publisher
Open Source
Last updated
Sep 26, 2026
Quick brief

Cortex is a source-backed API generation workflow for teams that want developer documentation, SDKs, and agent-facing MCP context to stay in sync. Use it when an operator needs an agent or release workflow to validate API specs, generate typed SDKs, build interactive documentation, and emit an MCP server that exposes typed tools, embedded specifications, SDK guides, and project docs. Invoke it instead of hand-maintaining docs or using a generic SDK generator when the goal is one repeatable generation plan across human developers and AI agents. The scope boundary is API-source-to-docs-SDKs-MCP generation, not a generic documentation site, SDK framework, or API platform listing.

How it works

What this skill actually does

Inputs and prerequisites: Node.js 20+, npm 10+, Cortex CLI, API specifications or Markdown sources.

Setup notes: Install with npm install –global @cortex-docs/cli, then run cortex init, cortex validate, and cortex generate to produce docs, SDKs, and the MCP server.

Source and verification boundary: use https://docs.cortexdocs.dev as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.