Context7

What a member can do

• Find a library by name and get its Context7 library ID.
• Fetch current documentation and code examples for a library, focused on a question or task.
• It only reads documentation: it has no tools that change anything.

Each task names the Context7 tools it may call. context7 on a task means every tool the Context7 server offers; a name such as context7.<tool> means that tool alone. A tool the task does not name is refused, whatever the connection allows.

Who connects it

A Context7 connection acts as the Context7 account that signed in when it was connected. It can do what that account can do, and no more.

Anyone who may change tools in your enterprise can connect Context7 for a member or a team. Connecting it for the whole enterprise is for the owner, and the people the owner allows.

A connection can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one above: task, then role, then member, then team, then enterprise. A connection on anything but a task also reaches the chat of every member it covers.

What waits for you

In a run, nothing on Context7 waits for you unless the task declares a gate on it. To approve each change before it happens, gate the tools that change something on the task. See Gates and tool scopes.

In a chat, a Context7 tool that its server does not mark as read-only asks you before it runs, unless you chose Always allow for that member and tool.

Setup

Before you connect

The free plan includes 1,000 API calls a month. Private repositories need a Pro or Enterprise plan.

Connect it

Context7 is an Express tool, so there is no server address, key or app to set up. Work in one browser window throughout: the sign-in returns to the portal in the window you started from.

1. In the portal, open the member's page → Tools. To connect it for a team or the whole enterprise, open Tools in the sidebar.
2. Under Express, find Context7 and choose Connect. On the Tools page you are asked who uses it: one member, a team or the whole enterprise.
3. Context7's sign-in opens. Sign in with the account the member should work as, and approve what it asks for.
4. You are back on Tools, and Context7 shows as connected.
5. Name the tools on the task, context7 for all of them or each by name.
6. Check it. Run a task that reads something from Context7. The run page shows the call and what came back.

You can take the access back at any time: delete the connection on Tools, or remove Zero Human OS from the connected apps in your Context7 account.

A first task to try

With Context7 connected, give a member a task that uses it. For example:

When I name a library and what I am building, fetch its current documentation and write a working example.

Start this task in the portal. It opens a conversation with your COO with the request written out. Read it, change what you like and send it. The COO asks what it still needs to know, then proposes the task for you to approve: its name, who owns it, its guardrails, the Context7 tools it may use and its instructions. Nothing is created until you approve it.