Skip to content

docs(readme): add positioning / comparison table (#472)#591

Merged
chronoai-shining merged 2 commits into
developfrom
docs/472-positioning-table
May 19, 2026
Merged

docs(readme): add positioning / comparison table (#472)#591
chronoai-shining merged 2 commits into
developfrom
docs/472-positioning-table

Conversation

@chronoai-shining
Copy link
Copy Markdown
Collaborator

Closes #472.

What

Adds ## How Ornn compares section after ## Quickstart — feature matrix against MCP servers, Smithery, and npm registry, plus a short prose section on what each comparison actually means.

Owns the CLI gap honestly via a footnote pointing at the Phase 2 roadmap, instead of marking ✓ on something we don't ship today.

Test plan

  • Pure docs, no runtime impact
  • Anchor #how-ornn-compares added to top nav

Inserts a "How Ornn compares" section after `## Quickstart` with
a feature matrix against MCP servers, Smithery, and npm registry,
followed by short prose on what each comparison actually means.

Owns the CLI gap honestly via a footnote pointing at the Phase 2
roadmap, instead of marking ✓ on a CLI we don't ship today. This
addresses the strategic-positioning callout in the issue: trim the
marketing to match what's actually built today, not what's planned.

Closes #472.
@chronoai-shining chronoai-shining merged commit 9b53961 into develop May 19, 2026
10 checks passed
@chronoai-shining chronoai-shining deleted the docs/472-positioning-table branch May 19, 2026 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Docs] Positioning / comparison table vs MCP servers + Smithery + npm in README

1 participant