Sign UpSign In
MCP Server
Integrations & Sync
The Lion Reader lion plugging a connector cable into a friendly robot AI assistant, linking the two together.

What is MCP?

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data sources. Think of it as a universal adapter that lets AI models like Claude interact with your applications in a secure, structured way. Instead of manually copying data between your feed reader and your AI assistant, MCP enables direct, programmatic access.

Lion Reader’s MCP server is built with the official MCP TypeScript SDK and supports two transports. Remote assistants such as claude.ai connect to the deployed app over Streamable HTTP, authenticating with OAuth 2.1 access tokens (or scoped API tokens). Local assistants such as Claude Desktop connect over stdio, keeping the connection entirely on your machine. Both transports register the same tools and call the same services layer.

Available Tools

The Lion Reader MCP server exposes a comprehensive set of tools that mirror the web UI’s capabilities:

  • list_entries — List feed entries with filters, search, and pagination
  • get_entry — Get a single entry with full content
  • mark_entries_read — Mark entries as read or unread in bulk
  • star_entries — Star or unstar entries
  • count_entries — Get entry counts with filters
  • save_article — Save a URL for later reading
  • delete_saved_article — Remove a saved article
  • upload_article — Upload Markdown content as an article
  • list_subscriptions — List and search active subscriptions
  • get_subscription — Get subscription details
  • list_tags — List tags with feed and unread counts
  • create_tag — Create a new tag
  • update_tag — Update a tag’s name or color
  • delete_tag — Delete a tag

Consistent Behavior

The MCP server uses the same services layer as the web UI, ensuring behavior is identical across interfaces. Whether you’re reading entries through your browser or asking Claude to summarize them, you’re accessing the same underlying data with the same permissions and filters.

Security and Usage

Remote access uses OAuth 2.1 access tokens carrying the mcp scope and audience-bound to the MCP endpoint, so a token minted for another service can’t be replayed here; scoped API tokens work too. Connect an OAuth client like claude.ai, or generate an API token with the mcp scope from your account settings. To run a local server for Claude Desktop and other stdio clients, use pnpm mcp:serve and point your assistant at it.