Advanced Usage

Configuration files, environment variables, and transport options for the Meldoc MCP server.

Configuration files

~/.meldoc/credentials.json

Stores authentication tokens and user information. Created automatically by auth login. Do not edit manually — use CLI commands. File permissions should be 600 (read/write for owner only).

~/.meldoc/config.json

Global settings, including the auto-cached workspace preference. See Workspace Management for how workspace selection and caching work.

{
  "workspaceAlias": "my-default-workspace"
}

meldoc.config.yml

Project-level workspace binding. When present, the MCP server uses this workspace automatically.

workspaceAlias: project-specific-workspace

Environment variables

MELDOC_ACCESS_TOKEN — Bearer token for the MCP server. See Authentication for how tokens are loaded.

MELDOC_MCP_TOKEN — An integration token the MCP server falls back to when no MELDOC_ACCESS_TOKEN or saved session is present. Tokens are resolved in order: MELDOC_ACCESS_TOKEN, your saved login session, then MELDOC_MCP_TOKEN.

MELDOC_TOKEN — CLI token for sync operations.

DEBUG — Enable debug logging.

Transport endpoints

Meldoc speaks MCP over two transports on the same base URL (https://api.meldoc.io):

Endpoint	Format	Best for
/mcp	Streamable HTTP	Claude Desktop, Claude.ai, Cursor, Claude Code, VS Code, Windsurf
/mcp/v1/rpc	JSON-RPC 2.0	meldoc CLI and standard MCP clients using mdc_ tokens

Both transports expose the same tools. See Getting Started with MCP for per-client configs.

File permissions

Keep credentials secure:

• ~/.meldoc/ directory — 700 (owner only)
• credentials.json — 600 (read/write for owner only)
• Add ~/.meldoc/ to your global .gitignore

What’s next?

Troubleshooting — Common issues and fixes.