Dwellir
Hosted MCP server for blockchain RPC across 150+ networks. Agents query chain state (EVM, Substrate, Solana, Bitcoin, Starknet, Sui), read Hyperliquid market data, sample WebSocket streams, check RPC usage, and manage Dwellir API keys. OAuth browser login, read-only chain access, no API key in client config.
호스팅형 MCP 서버
npx add-mcp 'https://mcp.dwellir.com/mcp'Claude Code, Codex, Cursor 등에 설치됩니다
문서
Dwellir MCP server
The hosted Dwellir Model Context Protocol server gives AI clients access to account tools and blockchain data. Connect it directly from an MCP client, or use it through the Dwellir plugin. The standalone server does not require the plugin or its skills.
The hosted server and dashboard account approval are available in production.
Connect a standalone client
Use an MCP client that supports remote Streamable HTTP servers and browser OAuth login. Add this server URL to your client's MCP settings:
https://mcp.dwellir.com/mcp
- Start the connection from your client and sign in to Dwellir in the browser.
- Check the requesting application on the dashboard.
- Choose Read only or Manage keys from the access options your client requested.
- Select Authorize. The browser returns to your client's callback automatically.
- Return to your client and confirm that the connection completed.
You can create a Dwellir account during login.
Select your client:
Claude Code
Codex
OpenCode
Grok
Cursor
claude mcp add --transport http --scope user dwellir https://mcp.dwellir.com/mcp
claude
# In Claude Code: /mcp → Dwellir → Authenticate
codex mcp add dwellir --url https://mcp.dwellir.com/mcp
codex mcp login dwellir
opencode mcp add dwellir --url https://mcp.dwellir.com/mcp
opencode mcp auth dwellir
grok mcp add --transport http dwellir https://mcp.dwellir.com/mcp
grok
# In Grok: /mcps → Dwellir → press i to authenticate
{
"mcpServers": {
"dwellir": {
"url": "https://mcp.dwellir.com/mcp"
}
}
}
For Cursor, merge the JSON into .cursor/mcp.json, then connect Dwellir in MCP settings.
Choose access in the dashboard from the scopes your client requests.
You do not need a local server or an API key in your client's configuration. The hosted server uses your selected Dwellir key when it makes blockchain requests. Those requests consume your account quota.
Available tools
| Task | Tools |
|---|---|
| Find chains, networks, and endpoint IDs | list_endpoints |
| Find supported read methods | rpc_methods |
| Query blockchain state | rpc_call |
| Query supported Hyperliquid Info data | hyperliquid_info |
| Sample WebSocket updates | capture_stream |
| Inspect account usage | usage_summary, usage_history |
| Manage named API keys | list_keys, create_key, update_key, delete_key |
| Find current documentation | search_docs, get_docs |
Discover an endpoint and an enabled key before making a chain query. The server returns non-secret key references, which identify keys within MCP. It does not return API key values in tool responses. Disabling or deleting a key interrupts applications that use it.
Read methods cover EVM, Substrate, Solana, Bitcoin, Starknet, and Sui. Method availability depends on the chain, endpoint, and account entitlements. Unknown methods and transaction broadcasts are rejected.
WebSocket captures contain at most 20 messages and run for at most 15 seconds. Continuous subscriptions and gRPC streams belong in application code. Use the Hyperliquid documentation for those protocols.
Project setup
Your application needs credentials that work outside the MCP connection. CLI 0.2.0 and later provide project setup through the Dwellir CLI. The commands below require CLI 0.2.0 or later.
dwellir auth login --device-code
dwellir project setup --chain ethereum --network mainnet --create-key my-project
The CLI writes the key and endpoint URLs into a private, ignored environment file.
The project setup command omits credential values from its output.
Keep generated environment files out of chat.
Use --key-name to select an existing enabled key by name.
The CLI also supports human use, CI automation, and custom usage tooling. It remains available independently of MCP and the plugin.
Permissions and disconnecting
Read access supports account inspection and chain queries. Manage keys also permits creating, updating, and deleting API keys. A read-only request cannot gain key-management access during approval. The MCP tools do not purchase subscriptions or execute trades.
Revoke the developer-tool credential from the dashboard's Agents page to end its account access. Also remove the connection from your client. Removing local credentials alone may leave server access active.
MCP or plugin?
Choose standalone MCP when you want tools in an existing MCP client. Choose the plugin when you also want Dwellir's reusable developer workflows and the canonical Hyperliquid skill. Both use the same hosted account and blockchain tools.