MCP.so
Sign In

Logseq MCP Server

@calvincchan

About Logseq MCP Server

No overview available yet

Basic information

Category

Memory & Knowledge

Runtime

node

Transports

stdio

Publisher

calvincchan

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Logseq MCP Server?

The Logseq MCP Server is a server-side application designed for local use with the Model Context Protocol (MCP). It communicates via the standard input/output (stdio) MCP transport and provides backend support for Logseq-related operations, built with Node.js and ES modules.

How to use Logseq MCP Server?

Clone the repository, install dependencies with npm install, create a .env file with a LOGSEQ_API_TOKEN variable, then start in development mode using npm run dev.

Key features of Logseq MCP Server

  • Integrates with the Model Context Protocol (MCP) via @modelcontextprotocol/sdk.
  • Communicates over standard input/output (stdio) MCP transport.
  • Supports REST API calls using axios.
  • Manages environment variables with dotenv.
  • Provides logging capabilities via winston.
  • Requires Node.js v22 or higher.

Use cases of Logseq MCP Server

FAQ from Logseq MCP Server

What runtime does Logseq MCP Server require?

Node.js v22 or higher.

How does Logseq MCP Server communicate with MCP clients?

It uses the standard input/output (stdio) MCP transport.

Does Logseq MCP Server require authentication or configuration?

Yes, it requires a LOGSEQ_API_TOKEN environment variable, which can be set in a .env file.

Is Logseq MCP Server intended for local use only?

Yes, the overview states it is designed for local use.

Comments

More Memory & Knowledge MCP servers