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: choose your account or an agent profile with selected access during authorization. Profile selection and setup.

  1. Endpoint: https://meinkontext.de/mcp — MCP Streamable HTTP, stateless, JSON response mode.
  2. OAuth discovery: https://meinkontext.de/.well-known/oauth-protected-resource/mcp.
  3. Header auth: send Authorization: Bearer <org API key> on every request.
  4. Reconnect after server-side tool or instruction changes — the catalog digest is delivered only at initialize.
  • With a personal OAuth connection, ask: “Set up meinKontext for this project using setup_client. Prefer relevant skills, memory and knowledge without repeated reminders.” Name the connection as configured in your client. Agent profiles and org API keys cannot run personal setup.
  • The tool returns a recipe; your agent checks the effective instruction file and adds only its marked routing block. Existing rules remain. It does not copy your context or switch off native memory, but it tells your agent to save lasting facts only in meinKontext. On request it can supply a local hook and rollback recipe; your client must install and trust it. Supported local versions get a project or user recipe; unknown versions and browser/cloud clients get session instructions. Start a new session afterwards.
  • Ask the agent to check with action: "check" or remove with action: "remove". A matching block hash confirms only the client-reported structure. Test a relevant task in a fresh session to see whether it actually reads the skill or memory. Keep the local installation receipt: it lets the agent remove its unchanged block even when the server is offline. Modified or duplicate blocks require reconciliation.
  • For other clients and agent profiles, ask for client_policy with the local connection alias. It returns versioned rules limited to your available tools; it needs no personal token and cannot expand access. A documented local adapter may load the owned section from an instruction file or inject it through a harness plugin. Without evidence of loading and safe update/removal, use session guidance. Persona files such as SOUL.md are excluded. A reported adapter is not verified autonomous behavior, and setup does not migrate tasks or switch sources.