Support

VS Code (GitHub Copilot) Setup

Connect Tempreon to VS Code and GitHub Copilot agent mode — mcp.json configuration, OAuth authorization, org policy requirements, and Visual Studio setup.

Overview

VS Code has native support for remote MCP servers. Once you add Tempreon, GitHub Copilot's agent mode can call Tempreon's tools directly from Chat — your AI loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns, across every tool you use.

Setup takes about two minutes: add the server, approve the OAuth prompt in your browser, and the tools appear in agent mode.

Quick path: Command Palette → MCP: Add Server → HTTP → paste the Tempreon URL → approve in the browser.

Prerequisites

  • VS Code 1.101 or later — earlier versions don't have full MCP support
  • A GitHub Copilot subscription. As of July 2026, on Copilot Business or Enterprise seats your organization's "MCP servers in Copilot" policy must be enabled — it's off by default, so an admin may need to turn it on. Free, Pro, and Pro+ personal plans aren't policy-gated.
  • A Tempreon account with at least one available Bridge slot
  • The Tempreon server URL (also shown in your Bridges dashboard)

Step-by-Step Setup

1. Add the server from the Command Palette

  1. Open the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows/Linux)
  2. Run MCP: Add Server
  3. Choose HTTP as the server type
  4. Paste the URL:
https://api.tempreon.com/functions/v1/tempreon-mcp/mcp
  1. Name it tempreon and choose whether to save it for this workspace or globally

2. Or edit the config file directly

For a workspace-level server, create .vscode/mcp.json:

{
  "servers": {
    "tempreon": {
      "type": "http",
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"
    }
  }
}

Naming quirk: VS Code's root key is servers — not mcpServers like most other clients. If you paste a config with mcpServers, VS Code silently ignores it.

For a user-level (all workspaces) config, run MCP: Open User Configuration from the Command Palette and add the same block. There's also a shell one-liner:

code --add-mcp '{"name":"tempreon","type":"http","url":"https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"}'

3. Authorize the connection

OAuth is automatic. When VS Code first connects, a browser tab opens to Tempreon's consent screen — sign in to your Tempreon account and approve. Back in the editor, an Auth CodeLens appears above the server entry in mcp.json; you can click it any time to re-authenticate.

4. Use it in agent mode

Tempreon's tools appear in agent mode in the Chat view. Open Chat, switch the mode picker to Agent, and check the tools picker — the Tempreon tools should be listed. Ask "What Tempreon tools do you have access to?" to confirm.

Troubleshooting

Config seems ignored. The root key must be servers, not mcpServers. This is VS Code's one naming quirk.

Don't see the MCP options at all? Confirm you're on VS Code 1.101+. On a Copilot Business or Enterprise seat, ask your org admin to enable the "MCP servers in Copilot" policy — it's disabled by default as of July 2026.

Tools don't appear in Chat. MCP tools only surface in agent mode, not ask or edit modes. Check the tools picker in the Chat view, and restart the server from the mcp.json CodeLens if needed.

Connection fails immediately. The URL must end in /mcp with no trailing slash.

Authorization never triggers. Click the Auth CodeLens above the server entry in mcp.json to start the OAuth flow manually.

Also connect: Cursor · Cline · JetBrains IDEs

Visual Studio

Visual Studio (2022 17.14+ and Visual Studio 2026) supports the same server through .mcp.json — either global at %USERPROFILE%\.mcp.json or per-solution as .mcp.json in the solution directory. The root key is servers, same as VS Code:

{
  "servers": {
    "tempreon": {
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"
    }
  }
}

When Copilot Chat loads the server, click the "Authentication Required" CodeLens to run the browser OAuth flow. Note that Visual Studio disables MCP tools by default — enable the Tempreon tools in the tool picker before using them. The same Copilot org policy applies on Business and Enterprise seats.

Try saying...

  • "Start my session." — triggers session_start to load your Core Imprint
  • "Search my knowledge base for our API design decisions." — exercises knowledge retrieval end-to-end
  • "Remember that we standardized on Vitest for this repo." — stores a decision for every future session