Context7 MCP connector for Manus

Write code against the current docs, not last year’s API

Say “Use Next.js 16 to add a check that sends signed-out visitors to /login.” Manus looks up that library and version in Context7, reads the current docs and code examples, then writes the code from them. Paste an error, and it checks how the API works now, tells you what changed and how to fix it. Put a version number in your prompt to get that version’s docs, or name a library ID such as /supabase/supabase to go straight to it.

First, connect Context7 in Manus

Use Next.js 16 to add a check that sends signed-out visitors to /login.

/vercel/next.js · v16Illustration

Send signed-out visitors to /login

Source: github.com/vercel/next.js · docs

In Next.js 16 the middleware file is called proxy.ts, and it exports a function named proxy.

import { NextResponse } from 'next/server'import type { NextRequest } from 'next/server'export function proxy(request: NextRequest) {  if (!request.cookies.has('session')) {    const login = new URL('/login', request.url)    return NextResponse.redirect(login)  }}

Writes proxy.ts from this snippet

Up-to-date documentation for AI, for the version you use

Name the library and version in your prompt. Manus looks up that version in Context7, reads its docs and code examples, then writes the code to match.

Libraries in this taskIllustration
/vercel/next.js/v16.2.9
/react/react/v19.2.7
/supabase/supabase/v1.26.04

Ask for a version by number

Write the version in your prompt, such as React 19 or Next.js 16, and Context7 matches the docs for that version.

Name the library ID to skip the search

If you know the ID, such as /supabase/supabase, put it in the prompt. Manus goes straight to that library’s docs without searching for it first.

An MCP for documentation: find the library, then read its docs

Context7 works in two steps. It finds the library and the versions it has, then reads the docs and code examples that answer your question. Each example comes with a link to its source.

Quick answers about one function

Ask how a function takes its arguments now, or which option replaced an old one. Manus answers from the snippet and shows where it came from.

Illustration
1Find the libraryresolve-library-id
LibraryNext.js
/vercel/next.js6,135 code examples
v16.2.9v16.1.6v15.1.11
2Read the docsquery-docs
Library ID/vercel/next.js/v16.2.9
QuestionHow do I read a cookie in proxy?
  • Read a cookie from the request in proxySource: github.com/vercel/next.js · v16.2.9
  • Set a cookie on the responseSource: github.com/vercel/next.js · v16.2.9

Fix a deprecated API error with the current docs

Paste the error and say which version you’re on. Manus looks up how that API works in your version, tells you what changed and rewrites the lines that break.

src/main.jsxreact 19.2Illustration
TypeError: ReactDOM.render is not a function
From the React 19 docsReact 19 removed ReactDOM.render. Render the app with createRoot from react-dom/client instead.
ReactDOM.render(<App />, document.getElementById('root'))import { createRoot } from 'react-dom/client'createRoot(document.getElementById('root')).render(<App />)

Paste the error and your version

Manus checks the docs for the version you name, explains in a sentence what changed and rewrites only the lines that need it.

Context7 docs for two versions, side by side

Before an upgrade, ask for both versions. Manus reads the docs for each and lists what changed, along with the docs it read.

Plan an upgrade from the docs

Get a table of what to rename and what works differently. Ask Manus to leave out anything the docs don’t show, so the list has no guesses.

Illustration
Next.js 15Next.js 16
Based on the Next.js 16 upgrade guide
Filemiddleware.tsproxy.ts
Functionexport function middleware()export function proxy()
Runs onedgenodejs
Config flagskipMiddlewareUrlNormalizeskipProxyUrlNormalize

The edge runtime isn’t supported in proxy. To keep using edge, keep middleware for now.

Use the latest version of each library in a full build

Context7 docs can guide a bigger job: a new web app, a change to your repository or every task in a project.

Build a web app on the current docs

Ask Manus to check Context7 for each library it uses, so a new web app starts on the APIs those versions have today.

Build and publish web apps

Update a repo, then open a pull request

With GitHub connected too, Manus makes the change in your repository and opens a pull request that lists the docs it followed.

See the GitHub connector

Make “check the docs first” a project rule

Put the rule in a project’s instructions. Shared instructions guide every new task in that project, so you don’t repeat it.

See how Projects work

Connect the Context7 MCP server to Manus

Context7 is already in Manus Connectors. Connect it once, and any task can look up current library docs before it writes code.

  1. Open Connectors

    In Manus, open Connectors, choose Context7 and select Connect.

  2. Finish connecting

    Context7 is already listed in Connectors, so there’s no server to install and no URL to paste. Follow the steps on screen to finish.

  3. Ask in any task

    Name the library and, when it matters, the version. Add “use Context7” when you want Manus to check the docs before it writes code.

Context7Current docs and code examples for each library

Get access to current, library-specific technical documentation and implementation examples through Context7 documentation service.

ConnectIllustration
  • Two tools: one finds the library, one reads its docs
  • Read-only: it looks up docs and doesn’t change your code or accounts
  • Each code example comes with a link to its source

Questions about Context7 MCP

How do I set up Context7 MCP in Manus? Do I need to install it or add a server URL or API key?

You don’t install anything or enter a server URL. Context7 is already in Manus Connectors: open Connectors, choose Context7, select Connect and follow the steps on screen. Manus doesn’t mark Context7 as a connector that needs extra setup, and its connector page doesn’t ask for a Context7 API key. Once it’s connected, name a library and version in any task.

Which libraries can Context7 look up?

The libraries that have been added to Context7, such as Next.js, React and Supabase. The community and library owners add them. Its search returns each match with a library ID, a count of code examples and the versions it has. If a library isn’t there, the search finds no good match, and you can ask Manus to read that library’s own docs site instead.

Can I choose which version’s docs it reads?

Yes. Put the version in your prompt, for example “Next.js 16”, and Context7 matches that version. You can also give a library ID with the version in it, such as /vercel/next.js/v16.2.9. To check which version was used, ask Manus to name the library ID it looked up.

Are the docs it finds always right?

Not always. The docs in Context7 come from the community and library owners, and Context7 says it can’t guarantee that every library is complete or accurate. Each code example it returns links to its source, so ask Manus to show the snippets and links it used, and check anything important.

How is this different from asking AI to write the code directly?

Without a lookup, the AI writes from what it learned in training, which can be older than the version you use. That is how renamed or removed APIs end up in new code. With Context7 connected, Manus reads the current docs for your version first and then writes the code.

Does Context7 see my code?

Its two tools take a library name or ID, a short question and, if known, the programming language. Neither takes your files or your repository. The question goes to Context7 to find the right docs, and the tool instructions tell the AI to leave API keys, passwords, personal data and private code out of it.

Is there a limit on how many lookups it can make?

Yes. Context7 sets rate limits on lookups, and its tools tell the AI to make no more than three calls per question. Naming the library and version up front helps each lookup find the right docs the first time.

Connect Context7 and code from the current docs

Connect Context7 in Manus