MCP Server

Overview

The Relinkia MCP server exposes your personal knowledge graph as structured memory for AI tools. Claude can query your notes, concepts, and connections directly — without you having to copy-paste content into the conversation.

In standard mode, two tools are available to Claude once the server is connected:

Requirements

Setup

Claude Desktop

First, generate an API token: Relinkia → Settings → Integrations → Generate MCP token. Then edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "relinkia": {
      "command": "npx",
      "args": ["-y", "@relinkia/mcp-server"],
      "env": {
        "RELINKIA_API_TOKEN": "<your-api-token>"
      }
    }
  }
}

Claude.ai (Remote MCP)

Claude.ai uses OAuth to connect to Remote MCP servers — no API token needed. Go to Settings → Integrations → Add MCP server and follow these steps:

1. Enter https://mcp.relinkia.app/sse as the server URL.
2. Click Add — claude.ai automatically initiates the OAuth authorization flow.
3. A Relinkia login and consent page opens in your browser.
4. Log in to Relinkia (if not already logged in) and click Approve.
5. You are redirected back to claude.ai — Relinkia tools are now available.

LangChain, n8n, or custom agents (REST)

The same tools are exposed over a standard REST API for non-MCP clients:

Base URL : https://api.relinkia.app/api/v1/agent/
Auth     : Authorization: Bearer <your-api-token>
Schema   : /api/v1/agent/openapi.json

relinkia_search

Semantic search across your knowledge base. Uses a hybrid pipeline (full-text + vector embeddings + Cohere reranking).

Parameters

relinkia_get_context

Context-aware search enriched by the current conversation. Same pipeline as relinkia_search, but the embedding and reranking are augmented by a conversation summary you provide.

Parameters

relinkia_get_context({
  q: "productive failure and learning",
  conversation_context: "Discussion on rethinking school assessment
    as a calibrated stimulus rather than a sanction. Parallel with
    Taleb's antifragility applied to education. Question about
    graduated exposure to error.",
  limit: 5
})

Understanding responses

Sources

Both tools return a sources array. Each source includes a title, a URL back to your note, a role, and the date it was last updated. Claude cites these as links — never as verbatim quotes.

"sources": [
  {
    "title": "Calibrated friction as stimulus",
    "url": "https://relinkia.app/note/{id}",
    "role": "argument_central",
    "last_updated": "2026-02-11"
  }
]

Possible roles: argument_central, external_source, emerging_connection, counter_argument.

Temporal advisory

If a retrieved note has been superseded by a more recent one, the response includes a temporal_advisory. Claude will surface this before drawing on the older note — to avoid presenting an abandoned position as your current thinking.

"temporal_advisory": "The most recent note on this point
  (11 February) nuances what you wrote in November.
  Mention this before relying on the older note."

Disambiguation

When a query matches several distinct clusters without a clear dominant match, relinkia_get_context returns a disambiguation_needed status instead of guessing. Claude will then ask you which thread to follow before answering.

{
  "status": "disambiguation_needed",
  "interpretations": [
    {
      "cluster": "Antifragility in finance",
      "note_count": 4,
      "hint": "Taleb notes, hedging, optionality"
    },
    {
      "cluster": "Antifragility in education",
      "note_count": 7,
      "hint": "More recent — graduated exposure to error"
    }
  ],
  "message_to_display": "You have two distinct threads on
    antifragility. Which one should I connect to our discussion?"
}

Quotas

Each call to relinkia_search or relinkia_get_context consumes one agent gesture.

* BYOK covers your own LLM costs. The platform fee (included in the 35€) covers the Relinkia RAG infrastructure (Qdrant, reranking) consumed by each call.

Owner Mode

Owner mode unlocks ten tools for account owners who want to use a personal AI agent to read and write their knowledge base directly. Unlike the standard mode — which returns gists and metadata — owner mode gives the agent access to the full text of notes and the ability to create or update them.

Typical use cases: maintaining a structured knowledge base with an AI assistant, syncing notes from external sources, or running automated pipelines that enrich your graph overnight.

Authentication

Owner mode requires a dedicated owner token — separate from the standard API token. Generate it in: Settings → Integrations → Generate owner token.

Pass it as a Bearer token in the Authorization header:

Authorization: Bearer <your-owner-token>

For Claude Desktop or MCP server config, use the RELINKIA_OWNER_TOKEN env variable:

{
  "mcpServers": {
    "relinkia-owner": {
      "command": "npx",
      "args": ["-y", "@relinkia/mcp-server"],
      "env": {
        "RELINKIA_OWNER_TOKEN": "<your-owner-token>"
      }
    }
  }
}

get_note_full

Retrieves the complete text content of a note by ID or document key. Returns the full body as a concatenation of all sections — unlike the standard search tools which return only gists.

Parameters

Response

{
  "noteId": "...",
  "title": "Architecture decisions",
  "body": "We chose event sourcing because...",
  "scope": "project-x",
  "docKey": "project-x-architecture",
  "type": "note",
  "currentVersion": 3
}

search_notes

Semantic search across owner notes, with an optional scope filter. Returns note titles, scopes, keys and current versions — not full body content. Use get_note_full to fetch the body of a specific result.

Parameters

get_by_doc_key

Retrieves a note by its document key (slug). Useful for deterministic access to well-known notes such as journals, configuration notes, or index pages.

Parameters

Returns the same format as get_note_full.

create_note

Creates a new note in the owner’s knowledge base. Returns the generated note ID. Optionally assigns a permanent document key for future deterministic access.

Parameters

Response

HTTP 201
{ "noteId": "683e4a2f1c9b..." }

Errors

update_canonical

Replaces the canonical body of an existing note. Uses optimistic concurrency: the server rejects the update if the note has been modified since you last read it. This prevents overwriting changes made by another agent or by the user in the app.

Parameters

Response

HTTP 200
{ "noteId": "683e4a2f1c9b...", "currentVersion": 4 }

Errors

list_scopes

Lists all scopes in the knowledge base with their volumetry — number of notes and decisions per scope.

Parameters

This tool takes no parameters.

Response

[
  { "scope": "project-x", "noteCount": 12, "decisionCount": 3 },
  { "scope": "architecture", "noteCount": 8, "decisionCount": 1 }
]

Decisions

Decisions are a distinct knowledge type from canonical notes. Where a canonical note can be superseded by a newer document, a decision is never superseded — it is only revised. Every revision is appended to a history[] array, preserving the full audit trail.

Use decisions to record choices that need a stable, auditable history — such as architectural decisions, configuration choices, or team agreements. Use canonical notes for knowledge that evolves and may be replaced.

create_decision

Creates a new decision with a stable semantic key. The key is immutable after creation and must be unique within the scope.

Parameters

Errors

update_decision

Revises an existing decision. The previous body is appended to history[] — decisions are append-only. Uses optimistic concurrency via baseVersion.

Parameters

Errors

get_decision

Returns the current body of a decision and its full revision history.

Parameters

Response

{
  "decisionKey": "auth-protocol",
  "scope": "architecture",
  "currentBody": "We use JWT with 1h expiry...",
  "currentVersion": 2,
  "updatedAt": "2026-07-15T10:23:00Z",
  "history": [
    {
      "version": 1,
      "body": "We use session cookies...",
      "updatedAt": "2026-06-01T08:00:00Z",
      "lastWriter": "claude-code"
    }
  ]
}

list_decisions

Lists all decisions in a scope with their current version and last update time.

Parameters

Response

[
  {
    "decisionKey": "auth-protocol",
    "currentVersion": 2,
    "updatedAt": "2026-07-15T10:23:00Z",
    "lastWriter": "claude-code",
    "summary": "Authentication protocol choice — JWT vs session cookies"
  }
]

Capabilities descriptor

Agents can query this endpoint at startup to discover what the server supports and adapt their behaviour accordingly — for example, skipping write calls if writeEnabled is false.

GET /api/ai/capabilities
Authorization: Bearer <your-owner-token>

{
  "protocolVersion": "canonical-docs/0.3",
  "ownerMode": true,
  "fullReadEnabled": true,
  "writeEnabled": true,
  "supportedWriteOperations": ["create_note", "update_canonical", "list_scopes", "create_decision", "update_decision", "get_decision", "list_decisions"]
}