VS Code on Context Board · connects in 1 minute

VS Code MCP Dashboard for GitHub Copilot

Copilot reads your priorities off your board and tells it what got done.

Start free trial
Free for 3 days · then $6 a month, the launch price · every connection included
Issues to triageSent by Copilotnow
  • Login redirect loops on Firefox#418 · bug2d
  • Add CSV export to reports#412 · feature4d
  • Docs: self-hosting with Docker#407 · docs6d
  • Rate limit the public API#399 · security9d
Copilotapp · fix/login-redirectnow
Working
Fixing the login redirect loop
Added a test for the Firefox case
This sprint
  • Fix the login redirect
  • Ship CSV export
  • Rate limit the public API
  • Write the Docker guide
StarsGitHubnow
2,148
3.2%this week
An example Context Board named Repo. Every number on it is example data.
ON ONE BOARD

Connect VS Code

  1. Click Add to VS Code In Connect, open Your AI, then VS Code, and click Add to VS Code. VS Code opens and asks you to install the board.
  2. Choose Allow When VS Code asks you to sign in, choose Allow on the board's page. No key to copy.
  3. Ask Copilot Open Copilot Chat and ask it to read your board, post an update or add a task.

Your agent works on your board, and everything it does carries its name and can be undone. How your agent works with the board

What to ask your agent

“Read my board and tell me what to work on first” Copilot reads your to-do list, your open issues and your numbers, then picks.
“Tick off 'fix the login redirect' on my to-do list” It finds the closest task by its words and checks it off. Nothing to open.
“Post an update to my board with what this branch changes and what is left” A line in Board activity you can read from anywhere, without opening VS Code.
“Put this repo's stars and open issue count on my board” Public GitHub numbers the board keeps live by itself, with no account or key.

What you see from VS Code

  • Your board read from Copilot Chat, to-do list and numbers included
  • Tasks added and ticked off as the work gets done
  • Updates in Board activity when Copilot finishes something
  • Copilot's current task in Agent activity, and its questions in Needs you
  • Every Claude Code and Codex session you run in VS Code, followed by the runner
  • Stars, open issues and forks for a public repo, kept live

VS Code on Context Board: the full guide

You start the day in VS Code. Your to-do list lives somewhere else, your issues are on GitHub, and the numbers that decide what matters this week are in three more tabs.

Add Context Board to VS Code and Copilot can see all of it from the chat.

What Copilot can do with your board

Read it: Ask what to work on first and Copilot reads your board before it answers. Your to-do list, the issues on it, the numbers you put there.

Keep the list honest: It ticks off a task when the work is done, and adds the ones it finds along the way.

Report back: It posts a line to the board’s activity feed when it finishes, and says what it is on in Agent activity. A question it needs you for lands in Needs you.

Add numbers: Ask for your repo’s stars or open issue count and it connects them as public data the board keeps live by itself.

Every change shows with Copilot’s name on it, and you can undo it.

Claude Code and Codex in VS Code

Plenty of people run Claude Code or Codex inside VS Code as well. The board follows those sessions without anyone asking. Link your computer once with the runner, and every Claude Code and Codex session shows in Agent activity with its title and project, working, done or waiting for you. The AI usage widget shows how much of each plan is left.

From your sessions, only names, states and percentages leave your computer. Never what was said in a session, and never your code.

Setting it up

In the board’s Connect window, open Your AI, then VS Code, and click Add to VS Code. VS Code opens and asks you to install the board. When it asks you to sign in, choose Allow. Then ask Copilot in the Chat view.

Rather edit the file? Add the board to .vscode/mcp.json as an http server with your board’s address. VS Code opens the same sign-in the first time it connects.

Frequently asked questions

Something else on your mind? Get in touch.

Does it work with GitHub Copilot?

Yes. VS Code hands an MCP server's tools to the agent in Copilot Chat, so once the board is installed, Copilot can read it and build on it. VS Code's MCP docs explain how servers become tools.

Can I add it without the button?

Yes. Add the board to .vscode/mcp.json as a server of type http with your board's address. VS Code opens the board's sign-in the first time it connects, and you click Allow.

Does the board see my code?

No. The board only gets what Copilot sends through the board's own tools, like an update, a status line, a task or a number. Your code stays in VS Code.

Does it change anything in VS Code?

It adds one MCP server to VS Code's settings, nothing else. Remove it there, or disconnect VS Code in the board's Connect window, and it stops working with your board at once.

Do my Claude Code and Codex sessions in VS Code show up too?

Yes, once you link your computer with the runner. Every Claude Code and Codex session shows in Agent activity with its title and project, whether it is working, done or waiting for you. From your sessions, only names, states and percentages leave your computer.

What does it cost?

Context Board is free for 3 days, then $6 a month at the launch price. One plan with every connection, widget and theme. Your GitHub Copilot plan is separate.

Go deeper

Keep reading

All integrations

Your business, on one board

Free for 3 days, then $6 a month at the launch price. One plan with every connection, widget and theme.

Start free trial See everything Context Board does