Context Book

io.github.aditya201551Published by GitHub account aditya201551v1.0.2Updated Oct 25, 2026

Stop re-explaining yourself to Agents. Give it the right context, right when needed.

VerifiedStreamable HTTPWeb executableDatabasesKnowledge & Memory

Overview

AI-generated overview

Context Book is a remote MCP server that gives an assistant a persistent, searchable library of Books and Pages, so context carries across conversations.

What you can do
Create and update Books and list or retrieve their metadata and pages, including all pages of a Book at once, with pagination for listings. Insert, replace or delete individual Pages inside a Book, with embeddings generated immediately on write. Run semantic search across all Books to pull the most relevant stored context. Fetch a usage guide once per session.
When to use it
Useful when you keep re-explaining the same background, preferences or project notes to an AI client and want that material stored once and retrieved on demand. Suited to Claude, Cursor, Windsurf and other MCP clients that should share a searchable knowledge library.
Requirements
A remote MCP endpoint reached over streamable HTTP; the README's self-hosting path instead needs Go, Node.js, PostgreSQL with pgvector and pg_trgm, and a Voyage AI API key. All tools require a valid Bearer token and are scoped to the authenticated user; the manifest declares no authentication setup.
Before you install
Tools write, replace and delete stored Pages, and page_delete does not renumber indices. Content is embedded through Voyage AI, so stored text is sent to that third party. Access depends on a Bearer token, which should be kept secret; the manifest declares no auth, so confirm how tokens are issued before connecting.

Installation

In SourceWeft

  1. Open Context Book in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.aditya201551%2Fcontext-book-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "context-book": {
      "type": "http",
      "url": "https://context-book-mcp-production.up.railway.app/"
    }
  }
}

README

[ContextBook]

[smithery badge] [License: MIT]

[ContextBook - Stop re-explaining. Give agents the right context | Product Hunt]

Stop re-explaining yourself to Agents. Give it the right context, right when needed.

LLMs are stateless — each conversation starts from scratch. ContextBook gives your AI tools a persistent, searchable knowledge library to draw the right context when they need it. No bloatware, no pre-loaded junk. Just the right information, at the right time.

How It Works

mermaid
flowchart LR    AI["🤖 AI Clients\nClaude · Cursor · Windsurf"]    Browser["🌐 Browser Dashboard"]    MCP["🔌 MCP Server :8081\n8 Bearer-authenticated tools"]    API["⚙️ REST API :8080\nOAuth 2.0 · Books · Pages · Search"]    DB["🗄️ PostgreSQL\npgvector · pg_trgm"]    VOYAGE["🧠 Voyage AI\nvoyage-4 (1024-dim)"]
    AI -- "MCP · Bearer Token" --> MCP    Browser -- "Session · HTTP JSON" --> API    MCP --- DB    API --- DB    API -- "OAuth 2.0 PKCE" --> AI    DB --- VOYAGE

Two Go binaries share a PostgreSQL database:

  • API server (cmd/api) — the control plane: user login, OAuth 2.0, dashboard, book/page CRUD
  • MCP server (cmd/mcp) — the data plane: 8 MCP tools for AI agents, protected by Bearer tokens

MCP Tools

All tools require a valid Bearer token and are scoped to the authenticated user.

ToolDescription
book_create_or_updateCreate a Book or update its metadata
book_listPaginated list of Book metadata
book_getRetrieve all pages of a Book
page_insertPush an atomic page into a Book; embeds immediately
page_updateReplace a page's content; re-embeds
page_deleteRemove a page (indices not re-numbered)
page_searchSemantic search across all Books
readmeReturns the usage guide (call once per session)

Quick Start

Prerequisites

1. Set up the database

sql
CREATE DATABASE contextbook_db;\c contextbook_dbCREATE EXTENSION IF NOT EXISTS vector;CREATE EXTENSION IF NOT EXISTS pg_trgm;

Migrations run automatically on API server startup.

2. Configure environment

bash
cp .env.example backend/.env# Edit backend/.env — set DATABASE_URL, API_KEY_SALT, VOYAGE_API_KEY

3. Run the backend

bash
cd backendgo run ./cmd/api/main.go    # API + dashboard (:8080)go run ./cmd/mcp/main.go     # MCP server (:8081)

4. Run the frontend (optional)

bash
cd frontendnpm install && npm run dev    # Vite dev server on :5173

5. Connect an AI client

For Cursor (.cursor/mcp.json):

json
{  "mcpServers": {    "contextbook": {      "url": "http://localhost:8081/mcp"    }  }}

For any MCP-compatible client, point the server URL to http://localhost:8081/mcp.

Documentation

  • Backend README — API routes, auth flows, database schema, MCP tools, configuration
  • Frontend README — components, routing, design system, development setup
  • Architecture — full system overview with Mermaid diagrams

Project Structure

context-book/├── backend/│   ├── cmd/api/main.go          REST API + auth server│   ├── cmd/mcp/main.go          MCP tool server│   └── internal/│       ├── api/                  REST handlers + routes│       ├── auth/                 OAuth 2.0 PKCE, sessions, SSO│       ├── context/              Book/Page business logic│       ├── db/                  pgx queries + migrations│       ├── embedding/            Voyage AI client│       ├── logger/               slog + HTTP access logging│       └── mcp/                  8 MCP tool handlers├── frontend/                     React 19 + Vite + TypeScript SPA│   └── src/│       ├── App.tsx               Router + app shell│       ├── lib/api.ts            HTTP client│       └── components/           UI components├── Dockerfile                    API server container├── Dockerfile.mcp                MCP server container└── go.work                       Go workspace

Contributing

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/my-feature)
  3. Make your changes
  4. Ensure the backend compiles (cd backend && go build ./cmd/api ./cmd/mcp)
  5. Ensure the frontend builds (cd frontend && npm run build)
  6. Commit and push
  7. Open a Pull Request

License

MIT — see the LICENSE file for details.

Source: README.md at commit 390bd24

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts