lcode 0.4.0: MCP servers

lcode now connects to MCP servers. Your local model can work with Jira and Confluence, GitHub, AWS, Google Drive, Grafana, Google Cloud, Sentry, Linear, Notion, Postgres, Kubernetes, a browser and any other MCP server. You approve every call.

lcode mcp catalog          # the ready-made servers
lcode mcp add atlassian    # signs you in through the browser, then tests the connection
lcode mcp add github       # offers the token from `gh auth token`
lcode mcp list             # checks every server and says what's wrong

Added

• Ready-made servers: lcode mcp add <name> sets up and tests each one:

  Server	Sign-in
  atlassian, sentry, linear, notion	browser sign-in
  google-drive	browser sign-in, with your own Google OAuth client
  github, grafana, postgres	a token or connection URL
  aws, gcp, kubernetes	your local credentials
  aws-knowledge, context7, playwright	nothing

  Servers that can change things start read-only where possible.

• Any other server: local (stdio) or remote (Streamable HTTP), configured in ~/.config/lcode/mcp.json in the standard mcpServers format, so a server's README snippet can be pasted in as is. A project can share servers in .mcp.json, used only after you approve it.

• Browser sign-in: OAuth 2.1 with PKCE, automatic client registration and token refresh. Tokens are stored readable only by you.

• Protocol versions: both the current MCP protocol (2026-07-28) and the earlier initialize-based versions.

• Context: when tool definitions would take more than 15% of the context window, the model looks tools up on demand instead (the mcp_tools setting). /mcp shows servers, tools and their context cost.

Fixed

• lcode bench: Ctrl+C no longer leaves a temporary folder behind, and the "already loaded" warning no longer names the model being benchmarked.

Docs: MCP servers

Upgrade

uv tool upgrade lcode-cli        # or: pipx upgrade lcode-cli

Full changelog: v0.3.1...v0.4.0