How do I use Zelta MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Zelta MCP Server show my recent projects" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

@finaegis/mcp

Connect Claude Desktop, Cursor, or Continue.dev to Zelta via the Model Context Protocol.

Install

npx -y @finaegis/mcp

Configure (Claude Desktop)

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "zelta": { "command": "npx", "args": ["-y", "@finaegis/mcp"] }
  }
}

First launch opens a browser for OAuth consent. The token is stored in your OS keychain (macOS Keychain, Windows Credential Manager, or Linux libsecret/gnome-keyring). Subsequent launches are silent.

If the OS keychain is unavailable — common on WSL2, Docker, Alpine, and headless Linux — the relay automatically falls back to a file at $XDG_CONFIG_HOME/finaegis-mcp/tokens.json with permissions 0600 (read/write for the owning user only). The file is plain JSON, not encrypted at rest. A one-line warning is printed to stderr the first time this happens.

Environment overrides

Variable	Default
`MCP_SERVER_URL`	`https://mcp.zelta.app/mcp`
`MCP_AUTH_SERVER`	`https://zelta.app`
`MCP_OAUTH_NO_BROWSER`	unset — set to `1` to print the auth URL instead of opening a browser
`FINAEGIS_MCP_TOKEN_STORE`	auto — set to `file` to force the file store, or `keychain` to require the OS keychain (errors if missing)

Troubleshooting

Browser does not open — set MCP_OAUTH_NO_BROWSER=1 and follow the URL printed to stderr.
Token expired — log out and re-auth: npx @finaegis/mcp --logout.
libsecret-1.so.0: cannot open shared object file — the keychain backend can't load. The relay handles this automatically and falls back to the file store; you can also force it with FINAEGIS_MCP_TOKEN_STORE=file.