meinKontextDocs
Navigation & search

Getting started

Connect your app

Client-specific setup with steps and commands.

Client setup

Choose your app and follow its setup steps. The guide explains the available sign-in options and any limitations.

OAuth browser login with your meinKontext account or an agent profile. Choose access.

  1. In a current VS Code with Copilot access, run MCP: Add Server from the Command Palette. Select HTTP, enter https://meinkontext.de/mcp and name it meinkontext.
  2. Choose Global → Copilot Global for Copilot harness sessions. The VS Code Local harness can use the user-profile configuration or .vscode/mcp.json shown below; merge the entry with existing servers.
  3. Start the server, follow the browser authorization prompt, and enable its tools in an agent chat.
  4. Ask: “Use meinKontext to list my available context objects. Do not change anything.” Inspect the actual list_objects call and result. An empty list may mean the profile has no granted objects.
json
{
  "servers": {
    "meinkontext": {
      "type": "http",
      "url": "https://meinkontext.de/mcp"
    }
  }
}
  • This is GitHub Copilot, not Microsoft 365 Copilot or Copilot Studio. Your organization must allow this MCP server. VS Code setup.
  • The example is the VS Code format. Portable Copilot configuration uses mcpServers; VS Code input variables are not forwarded to Copilot harness sessions. Configuration reference.
  • For terminal use, follow Copilot CLI; for GitHub-hosted tasks, follow Copilot Cloud.
  • If sign-in fails, check the environment and authorize again. Missing tools require checking profile access and tool selection. Reconnect after tool or instruction changes. A connection alone does not guarantee proactive memory or skill use.
  • Researched on 31 October 2026 from official documentation; a native Copilot login and tool call against meinKontext have not yet been verified.