nodemaven-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODEMAVEN_LOGIN | No | Optional. Proxy credential login to use instead of the account's own, e.g. a sub-user. | |
| NODEMAVEN_APIKEY | Yes | Required. API key from the NodeMaven dashboard. | |
| NODEMAVEN_PASSWORD | No | Optional. Proxy credential password to use instead of the account's own, e.g. a sub-user. | |
| NODEMAVEN_MCP_REVEAL_PASSWORD | No | Set to `1` to put the real password into `proxy_url` output. Off by default. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| proxy_urlA | Build a NodeMaven proxy string. |
| check_proxyB | Open one connection through the proxy and report the result. |
| test_proxy_on_siteA | Request one page of a site through the proxy and say whether it answered. |
| list_locationsA | List locations available for targeting, with the codes proxy_url takes. |
| account_statusB | Remaining traffic (bytes), subscription status and whether traffic is frozen. |
| traffic_statsB | Traffic used over time, as parallel labels and data arrays. Pass period, or start and end as dd-mm-yyyy (not ISO). Defaults to today. |
| top_domainsB | Domains reached through the proxy, largest traffic first, with bytes and request counts. Pass period, or start and end as dd-mm-yyyy (not ISO). Defaults to today. |
| list_sub_usersA | Sub-users of the account with their traffic usage and limits. No passwords. |
| create_sub_userA | Create a sub-user with its own proxy login. Changes the account. |
| update_sub_userB | Change a sub-user's traffic limit, or turn the limit on or off. Changes the account. |
| reset_sub_user_usageA | Set the recorded traffic of one or more sub-users back to zero. Changes the account. |
| delete_sub_userA | Delete a sub-user. Its proxy login stops working. Cannot be undone. |
| list_whitelist_ipsA | IP addresses allowed to use the proxy without a password, with their ports and targeting. |
| add_whitelist_ipA | Allow an IP address to use the proxy without a password. Changes the account. |
| remove_whitelist_ipA | Remove an address from the whitelist, by the id list_whitelist_ips or add_whitelist_ip gave. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools target clearly distinct resources and actions, and the descriptions make the boundaries readable. The only notable overlap is between check_proxy and test_proxy_on_site, which both test proxy behavior but differ in scope.
Names are consistently snake_case, and most action tools follow a verb_noun pattern. A few read-only/analytics tools use noun phrases instead, which is a minor deviation but still predictable.
With 15 tools, the set is well-scoped for proxy account management, covering analytics, sub-users, whitelist IPs, and proxy testing. Each tool appears to earn its place without obvious redundancy.
The surface covers the main lifecycle operations for sub-users and whitelist IPs, plus analytics and proxy testing. Some smaller gaps exist, such as no direct update for whitelist IP targeting or sub-user password reset, but these are workable around via remove/add or dashboard access.