VS Code

VS Code’s GitHub Copilot agent mode supports remote HTTP MCP servers natively (VS Code 1.99+). This integration ensures every Copilot developer seat has access to the exact same governed product context, regardless of their local machine configuration.

Click to enlarge

Technical Integration#

Follow these configuration steps to register the Think4Ever MCP server within your VS Code environment.

VS Code (GitHub Copilot)#

VS Code's Copilot agent mode supports remote HTTP MCP servers natively (VS Code 1.99+).

Step 1#

Create .vscode/mcp.json in your workspace (note: top-level key is servers , not mcpServers ):

{
  "servers": {
    "Think4Ever": {
      "type": "http",
      "url": "https://cell-ssm-use1-0005.us.portal.think4ever.com/mcp",
      "headers": { "Authorization": "Bearer tf_71b84ebb8284f86491f24b85311a55dfd2b0c9e74c678c7e" }
    }
  }
}

Or run MCP: Add Server from the Command Palette and pick HTTP . To make it available in every workspace, add it to your user configuration via MCP: Open User Configuration .

Step 2#

Open Copilot Chat in Agent mode and click the tools icon — the Think4Ever tools should be listed. Toggle on the ones you want active.

Step 3#

You can also reference tools directly in chat with # (e.g. #list_tasks ) to force a specific call.

VS Code Copilot Use Cases & Sample Prompts#

Integrating Think4Ever with GitHub Copilot anchors agent mode directly to your specifications, allowing code creation, documentation, and task tracking to happen side-by-side inside your workspace.