Skip to main content
Glama
kiseki-technologies

Kiseki-Labs-Readwise-MCP

by kiseki-technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
find_readwise_documents_by_namesB

Find documents in Readwise by a list of names.

Args:
    document_names (List[str]): The names of the documents to search for in Readwise.

Returns:
    Dict[str, Optional[Book]]: A dictionary where keys are the requested document names
    and values are the corresponding Book objects if found, or None otherwise.
list_readwise_documents_by_filtersA

List all documents in Readwise based on either category or date range At least one filter must be provided.

Args:
    document_category (str, optional): The category of the documents to list in Readwise.
        Allowed values are 'books', 'articles', 'tweets', 'podcasts', 'supplementals',
        or simply empty string '' if no category is specified. Defaults to "".
    duration_expression (Optional[str]): A duration expression to filter documents by creation date.
        Valid formats: "1w", "2h", "30m", etc.
    from_date (Optional[date]): The start date to filter documents (inclusive).
        Documents created on or after this date will be returned.
    to_date (Optional[date]): The end date to filter documents (inclusive).
        Documents created on or before this date will be returned.

Returns:
    List[Book]: A list of Book objects containing the documents from the specified category.

Raises:
    ValueError: If no filters are provided (all parameters are None or empty).
get_readwise_highlights_by_document_idsB
Get highlights from Readwise by document ids.

Args:
    document_ids (List[int]): The IDs of the documents to retrieve highlights for.

Returns:
    List[Highlight]: A list of Highlight objects containing the highlights from the specified document.

Raises:
    ValueError: If no document IDs are provided.
get_readwise_highlights_by_filtersA
Get highlights from Readwise by filters.

This function retrieves highlights from Readwise based on date range and/or tags.
At least one filter (from_date, to_date, or tag_names) must be provided.

Args:
    duration_expression (Optional[str]): A duration expression to filter highlights by creation date.
        Valid formats: "1w", "2h", "30m", etc.
    from_date (Optional[date]): The start date to filter highlights (inclusive).
        Highlights created on or after this date will be returned.
    to_date (Optional[date]): The end date to filter highlights (inclusive).
        Highlights created on or before this date will be returned.
    tag_names (List[str]): List of tag names to filter highlights by.
        Only highlights with at least one of these tags will be returned.

Returns:
    List[Highlight]: A list of Highlight objects matching the specified filters.

Raises:
    ValueError: If no filters are provided (all parameters are None or empty).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: finding documents by names, getting highlights by document IDs, getting highlights by filters, and listing documents by filters. There is no overlap in functionality, and the descriptions make it easy to differentiate between document-focused and highlight-focused operations.

Naming Consistency4/5

The naming follows a consistent verb_noun_by_filters pattern for three tools (find_readwise_documents_by_names, get_readwise_highlights_by_document_ids, get_readwise_highlights_by_filters, list_readwise_documents_by_filters), with 'find' and 'list' being slightly different verbs but still semantically clear. The structure is predictable and readable throughout.

Tool Count4/5

With 4 tools, the count is reasonable for a Readwise integration, covering core operations like retrieving documents and highlights. It might be slightly thin for a full-featured server, but it effectively handles key use cases without being overwhelming.

Completeness3/5

The toolset covers reading operations (finding and listing documents, retrieving highlights) but lacks create, update, or delete capabilities, which are common in CRUD workflows for a service like Readwise. This creates notable gaps that could limit agent functionality for managing documents or highlights.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources