Data · Local MCP server
LINZA
Local-first MCP sidecar for Markdown artifacts, review intents, and supervised knowledge growth.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Semiotronika/LINZA-MCP- Version
- 0.2.2
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-06-01
- Updated
- 2026-06-01
- Publisher
- Semiotronika (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Semiotronika) · how
- Repository
- github.com/Semiotronika/LINZA-MCP
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | linza-mcp | 0.2.2 | stdio |
How to connect LINZA
LINZA runs locally from a Python package published to PyPI: linza-mcp version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx linza-mcp. It reads these environment variables: LINZA_VAULT, LINZA_EMBED_PROVIDER, LINZA_EMBED_URL, LINZA_EMBED_MODEL, LINZA_EMBED_KEY (secret), LINZA_BRIDGE_THRESHOLD, LINZA_MAX_BRIDGE_PAIRS, LINZA_DEFAULT_PROFILE and LINZA_LANGUAGE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"linza-mcp": {
"command": "uvx",
"args": [
"linza-mcp"
],
"env": {
"LINZA_VAULT": "<value>",
"LINZA_EMBED_PROVIDER": "<value>",
"LINZA_EMBED_URL": "<value>",
"LINZA_EMBED_MODEL": "<value>",
"LINZA_EMBED_KEY": "<secret>",
"LINZA_BRIDGE_THRESHOLD": "<value>",
"LINZA_MAX_BRIDGE_PAIRS": "<value>",
"LINZA_DEFAULT_PROFILE": "<value>",
"LINZA_LANGUAGE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from Semiotronika (GitHub)
| Server | Runs |
|---|---|
| NouzSemantic knowledge engine for Obsidian with auto-classification and DAG hierarchy. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| LinkShrink MCPPrivacy-first URL shortener with analytics. | Local · stdio |
| LinkupSearch the web and fetch pages with sourced results, optimized for AI agents. | Local · stdio |
| LinkupSearch the web in real time to get trustworthy, source-backed answers. | Remote · HTTP, SSELive check: ✓ SSE reachable |
| lintlab SEO Site QACrawl a site for broken links, redirects and missing SEO tags. Pay per page on Apify. | Remote · HTTPLive check: sign-in required |
| LION - Trend Intent MCP + Marketplace Visibility AuditX402-paid MCP data: trend feed + visibility audit. USDC/Base. No API key. No PII. | Remote · HTTPLive check: ✓ handshake |
| LiongardMCP server for Liongard - inspectors, environments, metrics, detections, and timeline data. | Local · stdio |
| LiongardMCP server for Liongard - inspectors, environments, metrics, detections, and timeline data. | Local · stdio |
| Lipe Court RecordSearch page-cited evidence from the public court record in Lipe v. Lupus Superior. | Remote · HTTPLive check: ✓ handshake |