open-design vs python-sdk

open-design is much bigger: 94.2k stars against 24.2k. Over the days we have tracked them open-design moved +19.3% and python-sdk +2.2%, so open-design is growing faster right now.

open-design leads on context depth and customization. python-sdk does not take any axis by a clear margin.

Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.

Where they stand today

An open-source, local-first desktop alternative to closed design agents that turns local coding agents and a project's DESIGN.md into composable skills, plugins, and exportable real artifacts (HTML/PDF/PPTX/MP4).

Stars
94.2k
Tracked growth
+19.3%
Maturity
Last commit
2h ago
Language
TypeScript
License
Apache-2.0
Cost to run
Your API key or Open Design Cloud (paid)

The official Python SDK for the Model Context Protocol that provides first-class support for multiple transport modes (stdio, Streamable HTTP, SSE) and lets you build both MCP servers and clients with minimal code.

Stars
24.2k
Tracked growth
+2.2%
Maturity
Last commit
7h ago
Language
Python
License
MIT
Cost to run
Free, open-source
0%+19%52 tracked days
nexu-io/open-designmodelcontextprotocol/python-sdk

Six axes, head to head

Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.

Axisopen-designpython-sdk
Context depth
How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository.
Project-wide access
Diff only
Noise control
How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only.
No noise controls
None
Customization
How far it bends to your team: custom rules, prompts, style guides, per-path config.
Plugins & design-system
API-level customization
Privacy
Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only.
Self-hostable
Fully local
Model freedom
Whether you can point it at any provider, or it is wired to one.
Bring-your-own-key
Bring-your-own key
Setup ease
What it takes to get a first useful run out of it.
Quickstart 3 commands
One-command start

Which one to pick

Pick open-design if…

Local-first — run agent-native design workflows on your laptop with plugins and a DESIGN.md-driven design system, and export real files without relying on a single closed service.

  • Context depth: Project-wide access (4/5 against 1/5)
  • Customization: Plugins & design-system (5/5 against 3/5)
Runs in cli, coding-agent-plugin, ide, web-app. Works with byok, openai, anthropic, gemini, local-ollama.

Pick python-sdk if…

Easy setup — create a working MCP server or client in a few lines of Python and run it locally with a single command.

Runs in cli, web-app, ci. Works with byok.

What people want from each one

Questions people ask

Is open-design better than python-sdk?

open-design leads on context depth and customization. python-sdk does not take any axis by a clear margin. open-design is worth picking when local-first — run agent-native design workflows on your laptop with plugins and a DESIGN.md-driven design system, and export real files without relying on a single closed service.

Which of open-design and python-sdk keeps my code private?

open-design: Self-hostable (4/5). python-sdk: Fully local (5/5).

What does each one cost to run?

open-design: Your API key or Open Design Cloud (paid). python-sdk: Free, open-source.

Full profiles: nexu-io/open-design and modelcontextprotocol/python-sdk. Everything else in Tools & MCP.