Context7 with OHarness
- 连接器
- 开发者工具
Current docs and code examples for libraries. OHarness works with Context7 out of the box — sign in once in your browser and its tools are in every session.
本页正文为英文。它解释的术语是人们用英文检索的术语，而译过的术语已经是另一个术语。
What you get
| MCP connector | Remote, over streamable HTTP at https://mcp.context7.com/mcp. |
| Published by | Upstash |
How it signs in
Through your browser, the first time a session uses it. The server answers with a sign-in challenge, OHarness discovers Upstash’s authorization server and registers itself there on the spot, and the tokens land in ~/.oharness/auth.json, readable only by you. Nothing to paste, and nothing stored by us.
Try it
Once Context7 is connected, a first prompt to see it work:
Use Context7 to look into the bug in this branch and propose a fix with a test.
Adding it
- Download OHarness for the Mac, or install the CLI anywhere Node runs.
- In the composer, open the + menu and find Context7 under Connectors.
- Pick it and sign in when the browser opens. Its tools are available from the next turn.
Links
Common questions
Does OHarness work with Context7?
Yes. Context7 ships in OHarness as an MCP connector, so it is in the menu on first launch with nothing to look up.
How does the Context7 connector sign in?
Through your browser. The first request is answered with a sign-in challenge, OHarness registers itself with Upstash's authorization server on the spot, and the tokens are kept on your machine in auth.json, readable only by you. There is no key to paste.
Is OHarness affiliated with Upstash?
No. OHarness works with Context7 through its public MCP server; Context7 and its logo belong to Upstash.
More in developer tools
Chrome DevTools · Code simplifier · DeepWiki · Feature development · Frontend design · GitHub
Context7 and its logo belong to Upstash. Listed because OHarness works with it, not because Upstash endorses OHarness.
Use Context7 from OHarness
The same Context7 tools in every session, whichever of the model providers is underneath.