Connect your AI

Lectro is an MCP server. Add it to your AI app and the assistant can draft cited cards, fix flagged ones and quiz you, through the same tools the app uses.

The address

Every app below takes the same connector address:

The MCP address
https://app.lectro.ai/mcp

Signing in is OAuth: the app sends you to Lectro to allow access, so there is no key to paste. Everything a connected app writes is recorded under its name, and every edit it makes to a note keeps a revision you can revert.

Claude

  1. On claude.ai or the desktop app, go to Settings → Connectors → Add custom connector.
  2. Call it Lectro and paste the address.
  3. Allow access when Lectro asks, then switch the connector on from the tools menu in a chat.

ChatGPT

  1. Turn on Developer mode under Settings → Apps & Connectors → Advanced.
  2. Create a connector called Lectro with the address, using OAuth.
  3. Allow access when Lectro asks, then choose Lectro in a chat.

Cursor

Add the server under Cursor Settings → MCP, or in ~/.cursor/mcp.json, then sign in when Cursor asks:

Cursor MCP configuration
{
  "mcpServers": {
    "lectro": { "url": "https://app.lectro.ai/mcp" }
  }
}

Claude Code

Add it from a terminal, then run /mcp inside Claude Code to sign in:

Adding Lectro to Claude Code
claude mcp add --transport http lectro https://app.lectro.ai/mcp

What it can do

Every route a connector may call has a tool, so an assistant never falls back to HTTP. Tools that can discard scheduling or retire cards are marked destructive, so your app can ask you first. Managing your account and API keys has no tool at all.

AreaFor example
Today and sessionstoday, create_session, get_session, session_summary
Notessearch_notes, get_note, create_notes, update_note
Cards and reviewslist_cards, get_card, submit_review
Skill treeslist_trees, get_tree, create_tree_node, add_notes_to_node
Sourceslist_sources, create_source, add_citation
Notetypeslist_notetypes, create_notetype, add_notetype_template
Feedbacklist_feedback, resolve_feedback, get_style_guide
NextREST API →