NexaLayer

io.github.NexaLayerPublished by GitHub account NexaLayerv0.2.0Updated Oct 27, 2026

Managed proxy sessions, health, rotation, usage, and spend controls for AI agents.

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

NexaLayer lets an assistant browse proxy products, create and rotate paid proxy sessions, and check health, usage, budget and spend for AI agents.

What you can do
  • Browse the proxy product catalog with current prices and availability, filtered by type, country and stock
  • Read session details, health, usage, budget, alerts, balance and transactions
  • Create or rotate a paid proxy session, optionally returning proxy credentials
  • Change API-key and daily budget limits
  • Terminate a session when a task ends
  • Check service status, known issues, file and poll support tickets
When to use it
Use it when an agent needs managed proxy sessions and the owner wants the assistant to quote prices, create or rotate sessions, and track usage and spend against a budget. It suits workflows where purchases and policy changes should go through explicit owner approval.
Requirements
Runs locally over stdio, typically via npx with the npm package or a Docker image. Requires a NexaLayer API key in the NEXALAYER_API_KEY environment variable and network access to the NexaLayer API; NEXALAYER_BASE_URL is optional. An account with balance or trial credit is needed for paid sessions.
Before you install
Creating or rotating a session charges the account balance, and early termination does not imply a refund. Budget and API-key limit changes are policy writes. Credentials are returned only when include_credentials is true and should never be logged. The server keeps recent request ids and error codes and attaches them, plus client name and version, to support tickets; keys, proxy passwords and full URLs must not be included.

Installation

In SourceWeft

  1. Open NexaLayer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

NexaLayer MCP Server

This directory contains the MCP server package and implementation. For the repository overview, installation options, complete 16-tool catalog, and backend relationship, see the root README.

Connect an MCP client to NexaLayer products, sessions, health, usage, and spend controls.

json
{  "mcpServers": {    "nexalayer": {      "command": "npx",      "args": ["-y", "@nexalayer/mcp"],      "env": { "NEXALAYER_API_KEY": "agk_your_key" }    }  }}

The server writes protocol messages only to stdout. API errors go through MCP tool results. Tool annotations mark reads, paid writes, policy changes, and destructive cleanup so compatible clients can apply approval policies.

Tools

  • Read: products and exact prices, session detail, health, usage, budget, alerts, balance, and transactions.
  • Paid write: create or rotate a Session. Use a unique idempotency_key and owner approval.
  • Policy write: change API-Key and daily budget limits. Require owner approval.
  • Cleanup: terminate a Session when the task ends. Early termination does not imply a refund. If the upstream is down, billing stops at the first terminate attempt and NexaLayer retries the release in the background.
  • Support (no charge): nexalayer_check_status, nexalayer_known_issues, nexalayer_report_issue, and nexalayer_get_ticket.

nexalayer_list_products returns a compact, cursor-paginated catalog. It defaults to 20 currently available products, supports type, country, in_stock, limit, and cursor, and excludes internal pricing and supplier fields.

nexalayer_create_session incurs charges against the account balance. Read the current quote and budget, then obtain owner approval before calling it. POST /sessions does not honor include_credentials and omits proxy credentials. PRICE_MISMATCH (409): re-read prices, retry once. BUDGET_EXCEEDED and INSUFFICIENT_BALANCE (402): ask the owner, don't retry.

nexalayer_get_session and nexalayer_rotate_session accept optional include_credentials (default false) and pass it to the API. Credentials are omitted unless include_credentials=true; never log them.

Always read nexalayer_list_products before purchase because it returns the current openAgent-backed quote and availability. Exclusive static proxy sessions are $1.43–$5.86/month (launch pricing, live API authoritative).

text
nexalayer_list_products → nexalayer_get_budget → owner approval→ nexalayer_create_session → nexalayer_get_session → health/usage → nexalayer_terminate_session

Common API error codes include AUTH_INVALID_KEY, INSUFFICIENT_BALANCE, BUDGET_EXCEEDED, PRICE_MISMATCH, IDEMPOTENCY_CONFLICT, and RATE_LIMIT_EXCEEDED.

PRICE_MISMATCH is HTTP 409: re-read prices, retry once. BUDGET_EXCEEDED and INSUFFICIENT_BALANCE are HTTP 402: ask the owner, don't retry.

Errors and support

Failed API calls return an MCP tool error (isError: true) with a one-line summary and the full NexaLayer error object in structuredContent.error: code, retryable, retry_after, suggested_action, side_effects, doc_url, known_issue_id, and request_id. Branch on those fields, not on the message text.

When an error is not self-explanatory:

text
follow error.suggested_action → nexalayer_check_status → nexalayer_known_issues(error_code)→ nexalayer_report_issue → poll nexalayer_get_ticket after next_check_after_seconds

The server keeps the last 20 request ids and error codes it saw and attaches them to nexalayer_report_issue automatically, along with the MCP client name and package version. Never put API keys, proxy passwords, or full_url in a ticket. Response targets are early-access targets, not guarantees: S1 4h, S2 24h, S3 3 business days, S4 best effort. Human contact: [email protected] (Telegram @LEWISMIN).

Docker

Build the stdio MCP server from the repository root:

bash
docker build -t nexalayer-mcp ./mcp

The container can start and expose its tool catalog without credentials, which allows MCP directories and clients to inspect it safely:

bash
docker run -i --rm nexalayer-mcp

Pass the API Key only at runtime when calling NexaLayer tools:

bash
docker run -i --rm \  -e NEXALAYER_API_KEY="$NEXALAYER_API_KEY" \  nexalayer-mcp

NEXALAYER_BASE_URL remains optional. The image uses stdio and does not expose a network port or contain credentials.

Request an API key and one-time trial credit at https://nexalayer.net/agents?source=mcp-readme.

Source: mcp/README.md at commit 00db651

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

6
  1. v0.2.0LatestOct 19, 2026
  2. v0.1.6Oct 17, 2026
  3. v0.1.5Oct 16, 2026
  4. v0.1.4Oct 16, 2026
  5. v0.1.3Oct 15, 2026
  6. v0.1.1Oct 15, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts