Zelta MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@finaegis/mcp
Connect Claude Desktop, Cursor, or Continue.dev to Zelta via the Model Context Protocol.
First-time login
npx -y @finaegis/mcp --loginThis prints an authorization URL to the terminal and (where possible) opens it in your browser. After you complete consent, the token is persisted and the wrapper exits. You can re-run --login at any time to refresh credentials.
Related MCP server: MelviChat MCP Server
Configure (Claude Desktop)
Once logged in, add to claude_desktop_config.json:
{
"mcpServers": {
"zelta": { "command": "npx", "args": ["-y", "@finaegis/mcp"] }
}
}Token storage
By default, tokens are stored in $XDG_CONFIG_HOME/finaegis-mcp/tokens.json (typically ~/.config/finaegis-mcp/tokens.json) with file permissions 0600 (read/write for the owning user only). The file is plain JSON, not encrypted at rest.
Optional: OS keychain backend. If you prefer macOS Keychain / Windows Credential Manager / Linux libsecret, install keytar globally and opt in:
npm i -g keytar
FINAEGIS_MCP_TOKEN_STORE=keychain npx -y @finaegis/mcp --loginkeytar is not a dependency of this package — it's a native module that fails to install on common environments (WSL2, Docker, Alpine, CI). Keeping the default install pure JavaScript means npx -y @finaegis/mcp just works everywhere.
Environment overrides
Variable | Default |
|
|
|
|
| unset — set to |
|
|
Troubleshooting
Browser does not open — set
MCP_OAUTH_NO_BROWSER=1and 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— only happens if you opted intoFINAEGIS_MCP_TOKEN_STORE=keychainon a Linux system withoutlibsecret. Unset the variable (the default file store needs no native deps) or installlibsecret-1-dev+ a keyring daemon.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Connect AI agents to Replynodes over the Model Context Protocol.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Connect Claude, Cursor, or any MCP client to your FlowContent account
Related MCP Servers
- AlicenseCqualityFmaintenanceEnables AI agents and assistants like Goose or Claude to interact with VS Code through the Model Context Protocol.7675Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI clients like Cursor and Claude Desktop to interact with the MelviChat platform through the Model Context Protocol. It provides a standardized interface for consuming MelviChat API services within AI development tools.-
- AlicenseNot gradedqualityBmaintenanceExposes your local, Corral-organised workspace to AI coding agents via the Model Context Protocol, supporting tools like Claude Code, Cursor, Cline, and others.1GPL 3.0
- AlicenseNot gradedqualityBmaintenanceConnects ParaView to LLM assistants via the Model Context Protocol, enabling direct Python code execution and pipeline control within the ParaView GUI.5MIT