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. With a current Copilot CLI installed and signed into GitHub, run the command below. Alternatively, enter /mcp add in Copilot and select HTTP with the same URL.
  2. Open /mcp to inspect the connection. When authentication is needed, use /mcp auth meinkontext and complete the browser login.
  3. Ask: “Use meinKontext to list my available context objects. Do not change anything.” Verify the actual list_objects call and result.
bash
copilot mcp add --transport http meinkontext https://meinkontext.de/mcp
  • The user configuration is ~/.copilot/mcp-config.json and uses mcpServers. Copilot CLI does not read VS Code's .vscode/mcp.json. CLI setup.
  • A needs-auth status requires fresh authorization through /mcp auth meinkontext. Do not paste a bearer into command arguments or configuration files. CLI authentication reference.
  • Check organization MCP policy if the server is unavailable. Missing tools can reflect profile access; an empty object list can be valid. Reconnect after server-side tool or instruction changes.
  • For VS Code and the GitHub cloud agent, use their separate instructions.
  • Researched on 31 October 2026 from official documentation; native Copilot login/tool calls and proactive skill or memory adoption have not yet been verified.