@infolang/mcp-setup

Install InfoLang MCP for any client: print a pasteable snippet, merge into --out <file>, or use a known --client preset. Same OAuth / API-key flow as @infolang/cursor-setup, via @infolang/setup-core.

No hooks or rules — this CLI only configures the MCP server entry. For agent prompt guidance (auto_investigate / auto_memorize), see CURSOR_SETUP.md or CLAUDE_SETUP.md.

One-click install

Hosted https://api.infolang.ai/v1/mcp/ + client-native OAuth. Regenerate links with node scripts/generate-install-links.mjs from the services repo root.

Quick start (CLI)

npx @infolang/mcp-setup

Prints ready-to-paste mcpServers JSON (OAuth stdio gateway by default).

npx @infolang/mcp-setup --key il_live_YOUR_KEY --print

Hosted https://api.infolang.ai/v1/mcp/ + Bearer.

Write targets

# Arbitrary JSON (mcpServers schema; .bak backup, mode 0600)
npx @infolang/mcp-setup --out ./mcp.json --key il_live_YOUR_KEY

# Presets
npx @infolang/mcp-setup --client vscode     # .vscode/mcp.json (servers schema)
npx @infolang/mcp-setup --client windsurf   # ~/.codeium/windsurf/mcp_config.json
npx @infolang/mcp-setup --client gemini     # ~/.gemini/settings.json
npx @infolang/mcp-setup --client codex      # TOML print-only for ~/.codex/config.toml

OAuth (no --key) opens the browser (?client=mcp), stores session + backup key under ~/.config/infolang/, installs the durable gateway, and starts the local proxy on :17342 (LaunchAgent on macOS).

Proxy helpers

npx @infolang/mcp-setup proxy status
npx @infolang/mcp-setup proxy install
npx @infolang/mcp-setup proxy uninstall

Workspace sync (local Obsidian vault / markdown folder)

npx @infolang/mcp-setup workspace link ~/Notes --include "Projects/**" --include "Areas/**"
npx @infolang/mcp-setup workspace sync            # first sync always previews (dry-run)
npx @infolang/mcp-setup workspace sync --confirm  # actually sends
npx @infolang/mcp-setup workspace watch           # sync on file change
npx @infolang/mcp-setup workspace status
npx @infolang/mcp-setup workspace unlink <name>

Manifest-diff sync (only changed files/chunks are re-sent), thin wrapper over @infolang/setup-core/lib/{sync,vault-parse,vault-ignore,vault-link,workspace-cli}.mjs.

Privacy, non-negotiable: link requires explicit --include <glob> (repeatable) — never the whole vault by default (omit on a TTY to pick folders interactively). .obsidian/ and every binary/attachment are always excluded, and sync summaries always report what was skipped and why. The first sync on a fresh link is always a dry-run preview (files/chunks/bytes/destination) until --confirm is passed; link and the first sync print a disclosure of what leaves the device, where it goes, and how to remove it later.

Parsing coverage: wikilinks (incl. multiple [[links]] in one frontmatter field), embeds (![[...]], distinct from links), YAML frontmatter tags/metadata, .canvas (JSON Canvas), Dataview inline fields (key:: value).

Known limitation: production /v1/execute has been observed to reject a batched remember op (400 unknown op); sync falls back to bounded-concurrency individual /v1/remember calls. Namespace isolation is via the X-InfoLang-Workspace-Id header only — the body RememberRequest.namespace field is known to be ignored by the managed edge. See @infolang/setup-core/lib/vault-transport.mjs.

Local development

cd packages/mcp-setup
npm install
npm test

Docs

• docs/MCP_SETUP.md

Depends on @infolang/setup-core via file:../setup-core in the monorepo (switch happens only inside scripts/publish-npm-packages.sh for npm publish).

Publish

Publish @infolang/setup-core first (and overlay if core still needs a new release), then:

scripts/publish-npm-packages.sh mcp-setup
# or full ordered set:
scripts/publish-npm-packages.sh