Skip to main content
Glama
enesjakozh
readwiseio

Readwise MCP

Official
by readwiseio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

리드와이즈 MCP

사전 커밋

개요

MCP(모델 컨텍스트 프로토콜)는 애플리케이션이 대규모 언어 모델(LLM)에 컨텍스트를 제공하는 방식을 표준화하여 컨텍스트 관리와 LLM과의 직접적인 상호작용을 명확하게 분리합니다.

이 프로젝트는 LLM 클라이언트(예: Claude )와 Readwise 사이의 브리지 역할을 하도록 설계된 로컬 MCP 서버 입니다.

데모를 시청해보세요!

Related MCP server: Reader MCP Server

클로드에 설치

  1. Node가 설치되어 있는지 확인하세요.

  2. Claude 데스크톱 앱을 엽니다.

  3. 설정 > 개발자로 이동합니다.

  4. Edit Config 클릭합니다.

  5. claude_desktop_config.json 파일에 다음 항목을 추가하고 ACCESS_TOKEN 값을 Readwise 액세스 토큰 으로 바꿉니다.

지엑스피1

문제 해결

일반적인 문제 해결 지침은 공식 Model Context Protocol Claude Desktop 문제 해결 섹션을 참조하세요.

아래에는 우리가 접하고 해결한 일반적인 문제에 대한 구체적인 솔루션이 나와 있습니다.

"MCP 서버 Readwise MCP에 연결할 수 없습니다."

이런 문제가 발생하는 가장 큰 이유는 npx/Node 버전이 잘못 설정되었기 때문일 수 있습니다. nvm 사용 중이라면 터미널에서 nvm use 18 실행해 보세요. 그렇지 않다면 Node.js를 다시 설치하는 것을 고려해 보세요.

Readwise 도구 호출 시 오류 발생

이 MCP 서버를 사용할 때 Claude와 대화하는 동안 가끔 MCP 오류가 발생할 수 있습니다. 이러한 오류가 발생하는 경우, 다른 Claude 모델(예: Claude 3.5 Haiku에서 Claude 3.7 Sonnet으로)로 전환해 보는 것이 좋습니다. 이렇게 하면 문제가 해결되는 경우가 많습니다.

Available Tools

1 tool
search_readwise_highlightsD
ParametersJSON Schema
NameRequiredDescriptionDefault
vector_search_termYes
full_text_queriesYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.0.2
    • Changedsearch_readwise_highlights1 field changed
      • addedInput schema / properties / full_text_queries / maxItems
        Added value: +8
  2. 1 tool updatev1.0.0
    • First observedsearch_readwise_highlights
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

D1.7/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusing it with other tools. Its purpose is clearly identifiable from its name despite the missing description.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (search_readwise_highlights). With only one tool, naming consistency is inherently maintained.

Tool Count2/5

A single tool is far too limited for a Readwise MCP server, which would be expected to support listing, retrieving, tagging, or managing highlights in addition to searching.

Completeness1/5

The surface is severely incomplete: only a search operation is exposed, with no way to retrieve specific highlights, browse by tag, or perform any other meaningful Readwise actions. This creates a dead-end workflow for most use cases.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers