Web App

Next.js 15 app deployed on Vercel. The primary interface for browsing and managing the graph.

Dashboard

Landing page with stats and 8 category cards. Each card shows node count and 3 preview items — content sorted by most recent, entities by most connected.

Categories

Click any category to see a filtered list. Supports list, grid, and kanban layouts.

Search

Cmd+K global search across titles, descriptions, and content. Hybrid search: FTS5 + vector + Reciprocal Rank Fusion.

Graph Map

Interactive ReactFlow visualization of node connections.

Feed View

Chronological content feed with source text reader and format-aware rendering (transcript, markdown, raw).

Sidebar

Fixed left panel with all 8 categories (icon + count badge), Quick Add input at top for pasting any URL or text to ingest, plus search, guides, dimensions, and settings access.

Key Features

• Light/dark mode
• Real-time updates via SSE (node/edge/dimension changes broadcast instantly)
• Source reader with format-aware rendering
• Readonly mode for public deployments (NEXT_PUBLIC_READONLY_MODE=true)

---

MCP Server

The knowledge graph is accessible to any MCP-compatible AI agent via the Model Context Protocol. Published to NPM as latent-space-hub-mcp.

Quick Start

Add to your Claude Code, Cursor, or Windsurf MCP config:

{
  "mcpServers": {
    "latent-space-hub": {
      "command": "npx",
      "args": ["-y", "latent-space-hub-mcp"],
      "env": {
        "TURSO_DATABASE_URL": "your-turso-url",
        "TURSO_AUTH_TOKEN": "your-turso-token"
      }
    }
  }
}

Architecture

The standalone MCP server (apps/mcp-server-standalone/) connects directly to Turso via @libsql/client. It runs as a stdio process — the MCP client spawns it as a subprocess.

AI Agent (Claude Code / Cursor / Discord Bot)
    ↓ stdio
latent-space-hub-mcp (Node.js process)
    ↓ libsql
Turso cloud SQLite

All 18 Tools

Search & Discovery

Read

Write

Guides

Setup Options

Security (Public Deployment)

---

Discord Bot — Slop

Slop is the community bot. Opinionated, source-grounded, member-aware. Backed by the full knowledge graph via MCP tool-calling.

How Slop Uses MCP

Slop has direct tool-calling access to 9 read-only MCP tools. The tools are passed to the LLM via OpenRouter's tool-calling API. The LLM decides what to search — same as how Claude Code uses MCP tools.

User message in Discord
    ↓
Discord.js receives message
    ↓
Bot builds system prompt (soul + guides + member context)
    ↓
Sends to OpenRouter WITH tool definitions
    ↓
LLM decides: call ls_search_nodes? ls_search_content? ls_sqlite_query?
    ↓
Bot executes tool calls via MCP (stdio → latent-space-hub-mcp → Turso)
    ↓
Tool results fed back to LLM
    ↓
LLM may call more tools (up to 5 rounds) or generate final response
    ↓
Response posted to Discord thread with source links

Slop's 9 Read-Only Tools

The agentic loop runs up to 5 rounds. Tool results are truncated to 4000 chars to prevent context blowout. Write operations (member updates, edge creation) are handled by the bot code directly, not through the LLM's tool calls.

Interaction Points

@Slop Mentions

Mention @Slop in any allowed channel. Slop creates a thread (Slop: [topic]), searches the graph, and responds with a source-grounded take. Follow-up messages in the thread continue the conversation.

Slash Commands

Automated Kickoff

When new content is ingested, the hub calls Slop's internal API (/internal/kickoff). Slop creates a thread, searches the graph for context on the new content, and generates an opening take. Community joins from there.

Member Memory

/join creates a member node in the knowledge graph with Discord metadata.

On each interaction:

1. Slop looks up member profile and injects context into the system prompt
2. After responding: appends interaction summary to member notes
3. Updates last_active, interaction_count, discovered interests
4. Creates member → content edges for topics discussed

All member updates are non-blocking (run after the response is sent).

Persona

Defined in personas/slop.soul.md. Key traits:

• Provocative but source-grounded
• Attacks ideas, never people
• Cites specific content with links
• Uses the knowledge base as ammunition for hot takes

Footer

Every response includes:

• Model badge: claude-sonnet-4-6
• Tools footer: search_nodes(x2) | search_content | get_nodes — shows exactly which MCP tools the LLM called

---

Announcements Webhook

One-way webhook from Vercel → Discord. Not a bot — just formatted messages posted via Discord webhook URL.

What It Posts

When the hourly ingestion cron finds new content:

1. #announcements — Clean card with emoji header, title, event date, chunk count, and source link
2. #yap kickoff (fallback mode) — Mentions @Slop with a prompt to discuss the new content

The webhook uses a shared identity ("Latent Space Hub") with configurable avatar.

Webhook vs Bot Kickoff

The bot API mode is preferred because Slop searches the knowledge graph with its own tools and produces a richer, more contextual opening post.