Dwellir plugin

The Dwellir plugin combines the hosted MCP server, account tools, and developer skills. You can also connect the MCP server independently from a compatible client. Use it to inspect RPC usage, query blockchain data, and manage API keys.

Version 0.1.0 is available for private testing. Public directory installation is not available yet. The hosted MCP server and dashboard account approval are available in production. The Dwellir CLI and Hyperliquid skill are available separately.

How account access works

Connect your Dwellir account through the plugin's browser login flow. Check the requesting application on the dashboard. Choose Read only or Manage keys from the access options your client requested, then select Authorize. The browser returns to your client's callback automatically. Return to your client and confirm that the connection completed. You can create an account during login. Revoke access from the dashboard's Agents page when you finish. Also remove the connection from your client. Removing local credentials alone may leave server access active.

With Manage keys access, the hosted server can create, rename, enable, disable, and delete API keys. Read-only access permits listing keys and querying blockchain data. It returns key names and non-secret references. Direct blockchain queries use the selected key on the server and consume your account quota.

Query blockchain data

Discover an endpoint before selecting a method. The first release supports registered read methods across EVM, Substrate, Solana, Bitcoin, Starknet, and Sui. Method support depends on the chain and endpoint.

For Hyperliquid, use the Info tool for supported queries. The stream tool captures short WebSocket samples, including order book updates. Samples contain at most 20 messages and run for at most 15 seconds. Build continuous streams and gRPC clients in your project using the Hyperliquid references.

Example requests:

• "Show my Dwellir RPC usage this month."
• "Find an Ethereum mainnet endpoint and query the latest block."
• "Help me build a Hyperliquid order book consumer."
• "List my API key references without exposing key values."

Planned project setup

Independent applications need their own API key configuration. CLI 0.2.0 will let your coding agent set up project credentials through the plugin workflow. You do not need to copy credentials into chat.

The commands below are planned and unavailable in the current release.

dwellir auth login --device-code
dwellir project setup --chain ethereum --network mainnet --create-key my-project

Use device login when a browser cannot reach a terminal's localhost callback. For local development, the existing dwellir auth login flow remains available.

Project setup writes DWELLIR_API_KEY, DWELLIR_RPC_URL, and DWELLIR_WSS_URL into .env. Use --env-file .env.local for frameworks that expect that filename. Use --key-name to retrieve an existing enabled key by name. The CLI adds an ignore rule and refuses tracked environment files.

Application code reads these environment variables. The project setup command omits credential values from its output. Keep generated environment files out of chat. Store deployment credentials in your hosting provider's secret store.

Skills and source

The plugin includes a general Dwellir skill and the existing Hyperliquid skill. Hyperliquid references remain maintained in their canonical repository. Each plugin build bundles a pinned revision of those same files.

• Canonical Hyperliquid skill
• Dwellir CLI
• Agent tooling