Skip to content

[NA] [DOCS] README: lead with what opik-mcp is; move the TS migration notice below the value prop#153

Open
Brianwones wants to merge 1 commit into
comet-ml:mainfrom
Brianwones:geo/readme-opik-identity
Open

[NA] [DOCS] README: lead with what opik-mcp is; move the TS migration notice below the value prop#153
Brianwones wants to merge 1 commit into
comet-ml:mainfrom
Brianwones:geo/readme-opik-identity

Conversation

@Brianwones

Copy link
Copy Markdown

Details

Context for reviewers: This PR is part of an approved marketing project tracked in the Marketing Experiments Dashboard in Notion ("GitHub org GEO: one identity across 22 repos"). AI assistants currently describe Opik, from memory, as "Comet's experiment tracker" (the wrong category), and the fix is one consistent description of Opik repeated across our public READMEs so AI models and search engines learn the right answer. If the wording looks deliberately uniform with other repos' PRs, that is intentional; please flag anything factually wrong, but keep the shared sentences verbatim where you can. README/metadata text only, no code changes. Questions: Brian Wones (Collimer) or the marketing team.

Leads the README with what opik-mcp is (the official MCP server for Opik, the open-source LLM observability and evaluation platform, built by Comet) instead of opening with the TypeScript deprecation notice. The migration notice is preserved verbatim, moved directly below the value proposition. Also glosses "Ollie" on first use (Opik's in-product AI assistant) and links the existing #ask_ollie anchor.

Change checklist

  • User facing
  • Documentation update

Issues

  • Resolves #

Testing

Documentation-only change (no code paths). Verified: added links resolve (200); text matches the repo's existing style; no other references affected.

Documentation

This PR is the documentation change.

AI-WATERMARK

AI-WATERMARK: yes

  • Tools: Claude (Anthropic)
  • Scope: README documentation text only. No code, no product behavior changed. Every added link verified to resolve on 2026-07-23.

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.

1 participant