Sqlite Literature Management Fastmcp MCP Server

🚀 Universal Source Management System

A flexible system for managing various types of sources (papers, books, webpages, etc.) and integrating them with a knowledge graph.

🚀 Quick Start

This system integrates with the MCP Memory Server for persistent knowledge graph storage.

1. Create a new SQLite database using our schema:

# Create a new database
sqlite3 sources.db < create_sources_db.sql

2. Install the source management server:

# Install for Claude Desktop, specifying the database path
fastmcp install source-manager-server.py --name "Source Manager" -e SQLITE_DB_PATH=/path/to/sources.db

✨ Features

Core Features

• Unified source identifiers using an internal UUID system.
• Support for multiple source types (papers, webpages, books, videos, blogs).
• Multiple identifiers per source (arxiv, DOI, Semantic Scholar, ISBN, URL).
• Structured note management with titles and content.
• Tracking status (unread, reading, completed, archived).

Entity Integration

• Link sources to knowledge graph entities.
• Track relationships between sources and entities.
• Flexible relationship types (discusses, introduces, extends, evaluates, etc.).
• Integration with the memory graph.

📦 Installation

This system integrates with the MCP Memory Server for persistent knowledge graph storage.

💻 Usage Examples

Basic Usage

Adding Sources

# Add a simple paper source
add_source("Title", "paper")

# Add a source with multiple identifiers
add_source(
    title="Title",
    type="paper",
    identifiers={
        "arxiv": "1234.5678",
        "doi": "10.xxxx/1234"
    },
    status="unread"
)

Viewing Sources

# Display all sources
view_sources()

# Display detailed information for a specific source
view_source("source_id_1")

# Display notes for a source
view_notes("source_id_1")

📚 Documentation

Database Schema

Core Table Structure

-- Source table
CREATE TABLE sources (
    id UUID PRIMARY KEY,
    title TEXT NOT NULL,
    type TEXT CHECK(type IN ('paper', 'webpage', 'book', 'video', 'blog')) NOT NULL,
    identifiers JSONB NOT NULL,
    status TEXT CHECK(status IN ('unread', 'reading', 'completed', 'archived')) DEFAULT 'unread'
);

-- Source notes
CREATE TABLE source_notes (
    source_id UUID REFERENCES sources(id),
    note_title TEXT NOT NULL,
    content TEXT NOT NULL,
    created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (source_id, note_title)
);

-- Entity links
CREATE TABLE source_entity_links (
    source_id UUID REFERENCES sources(id),
    entity_name TEXT,
    relation_type TEXT CHECK(relation_type IN ('discusses', 'introduces', 'extends', 'evaluates', 'assesses', 'assesses', 'assesses')),
    PRIMARY KEY (source_id, entity_name)
);

🔧 Technical Details

Core Features

• Unified Identifiers: Generate unique identifiers for each source using an internal UUID system.
• Multiple Type Support: Include multiple source types such as papers, webpages, books, videos, and blogs.
• Multi-Identifier Support: Each source can have multiple identifiers, such as arxiv, DOI, Semantic Scholar, ISBN, and URL.
• Status Management: Track the status of sources, including unread, reading, completed, and archived.

Data Organization

• Structured note management, with each note having a title and content.
• Classification by source type.
• Tracking relationships between sources and knowledge graph entities.
• Managing changes in source status.

🤝 Contribution Guidelines

1. Fork the repository
2. Create a feature branch
3. Add tests for new features
4. Submit a pull request