For AI agents: a documentation index is at /llms.txt. Every page is also available as markdown, just append .md to the URL.
Overview
VS Code reads MCP servers from anmcp.json file and exposes their tools in agent mode. You add Reap as an HTTP server, sign in through OAuth, and pick the workspace VS Code is allowed to use.
VS Code uses a different JSON shape than Cursor: the top-level key is
servers (not mcpServers), and remote servers need "type": "http".Before You Start
- Your Reap workspace must be on a paid plan with API access enabled.
- Use a recent version of VS Code with GitHub Copilot enabled, and switch the Chat view to Agent mode.
- You need access to the Reap workspace you want to connect.
Reap MCP Server URL
Add Reap To VS Code
1
Choose workspace or global
For a single project, create
.vscode/mcp.json in the project root. To make Reap available everywhere, open the Command Palette and run MCP: Open User Configuration, which opens the mcp.json in your user profile.2
Add the Reap server
3
Start the server
Save the file. VS Code shows a Start action above the server entry. Click it, or run MCP: List Servers from the Command Palette and start reap.
4
Sign in to Reap
VS Code prompts you to allow the server to sign in. Accept, then sign in to Reap, select the workspace VS Code is allowed to use, and click Authorize. Close the tab when you see Authentication successful.
5
Enable the tools in agent mode
Open the Chat view, switch to Agent mode, and click the tools icon to confirm the Reap tools are selected.
Confirm The Connection Works
Run MCP: List Servers from the Command Palette. reap should be running. Then ask in agent mode:Use Reap From VS Code
Troubleshooting
- Server does not start? Check the JSON shape. VS Code needs
serverswith"type": "http". ThemcpServerskey is Cursor’s format and will not work here. - No tools in chat? Reap tools only appear in Agent mode. Switch modes, then check the tools picker.
- Stuck unauthenticated? Run MCP: List Servers, stop and restart reap, and accept the sign-in prompt.
- Wrong workspace? Restart the server, re-authorize, and pick the correct workspace on the Reap authorization screen.