Documentation

MCP, channels & the Hub

Tools (MCP)

MCP servers give every run extra tools — files, browsers, APIs, databases. Lectern ships a verified catalog (25 servers: GitHub, Postgres, Notion, Sentry, Stripe, Firecrawl, E2B and more) with requirement-aware forms, plus a full-page library behind Browse all. One add registers the server across Claude Code, OpenCode, and Antigravity together, with truthful per-agent chips showing exactly where it landed. Status is live: running vs registered vs failed — capped probes, never a frozen UI.

In a chat, /mcp lists what's connected and /mcp github targets one for your next message.

Live demo · one add registers everywhere

Channels — remote access

Different from MCP: channels let a messaging app reach your agent. Pair Telegram once and task your machine from your phone — send a prompt, get completion pings back. Powered by Claude Code's channel system; strictly allowlist-gated (approvals happen in the CLI on your machine, never from a chat message).

Live demo · task your PC from your phone

The Hub & skills

Record a GUI demonstration with /record — it becomes a replayable skill (deterministic replay, no re-reasoning).
Write or import skills as portable JSON; they sync into Claude Code automatically.
Community hub — a Git-backed index (ShrimpScript/lectern-community) with official and ecosystem tiers (curated collections from Anthropic, Vercel, and the wider skills world link out with attribution), an in-app docs viewer, and review-before-install. Publishing runs a $0 AI audit gate before anything ships.
Skill stats — every skill tracks uses and outcomes; pause the ones you don't want auto-applied.

Lectern's brain is also an MCP server itself — Connect Lectern's brain in Settings exposes memory + skills as tools to any MCP client.

Next: Back to overview →