What runtime does Logseq MCP Server require?
Node.js v22 or higher.
@calvincchan
Basic information
No overview available yet
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
@modelcontextprotocol/sdk.axios.dotenv.winston.—
Node.js v22 or higher.
It uses the standard input/output (stdio) MCP transport.
Yes, it requires a `LOGSEQ_API_TOKEN` environment variable, which can be set in a `.env` file.
Yes, the overview states it is designed for local use.

Local AI agent for your Mac with a built-in MCP server: 18 tools for your notes and PDFs, a temporal memory graph, an on-device LLM and a neural voice. No account, no telemetry. No data centers required.

Model Context Protocol Servers

Exact, shared memory for AI agents: a hierarchical database where totals always add up, every write is attributed to the agent and person behind it, and any figure traces back to its source file. Agents create databases,
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 162 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab
Comments