noya-agent-mcp

A thin stdio ↔ HTTP proxy that bridges local MCP clients (Claude Desktop, Cursor, VS Code, etc.) to the Noya HTTP MCP server at https://agent-api.noya.ai/mcp.

Full documentation: mcp.noya.ai — tool references, examples, and usage guides.

All tools, wallets, authentication, rate limiting, and routing live server-side. This binary is a ~100-line JSON-RPC relay with zero tool knowledge — whenever the server gains a new tool, it is immediately available to your local client without updating the proxy.

What you get

Connecting through this proxy exposes the full Noya tool surface:

• 100+ noya_data_* tools — crypto prices, TVL, funding rates, on-chain analytics, prediction markets, news, sentiment (no wallet needed).
• Conversational agent tools — noya_send_message, noya_list_threads, noya_get_thread_messages, noya_delete_thread, noya_get_agent_summary, noya_generate_thread_id.
• On-chain AgentKit tools — wallet operations, ERC-20 transfers, swaps, faucets, etc., backed by a per-user Privy wallet provisioned server-side. No CDP keys, no local private keys.
• x402_fetch — make HTTP requests with automatic x402 payment negotiation, signed by your server-side wallet.
• noya_read_docs — pull Noya docs on demand.

Prerequisites

1. Create an account at agent.noya.ai.
2. Generate an API key from Settings → API Keys.
3. Store the key securely — it is shown only once.

Installation

Using npx (recommended)

No installation needed. Configure your MCP client to run:

{
  "mcpServers": {
    "noya-agent": {
      "command": "npx",
      "args": ["-y", "noya-agent-mcp"],
      "env": {
        "NOYA_API_KEY": "noya_your_key_here"
      }
    }
  }
}

Global install

npm install -g noya-agent-mcp
NOYA_API_KEY=noya_your_key_here noya-agent-mcp

Configuration

| Variable | Required | Default | Purpose | | -------------- | -------- | ------- | --------------------------------------------------------------- | | NOYA_API_KEY | Yes | — | Your Noya API key (noya_...). Sent as the x-api-key header. |

That's it — no CDP keys, no wallet secrets, no data-endpoint URLs, no timezone.

How it works

Claude Desktop  ──stdio──>  noya-agent-mcp
                               ├─ StdioServerTransport
                               └─ StreamableHTTPClientTransport
                                      │
                                      └──POST /mcp──>  noya-agent-lang
                                                         (all tools, auth, wallets)

The proxy creates a StdioServerTransport to receive JSON-RPC from the local MCP client and a StreamableHTTPClientTransport pointed at the Noya HTTP MCP endpoint. Every initialize, tools/list, tools/call, and notification is forwarded in both directions. The HTTP transport handles mcp-session-id and mcp-protocol-version header negotiation transparently.

Upgrading from 2.x

3.0 is a breaking change. The local wallet model has been removed. All the CDP_* environment variables, NOYA_BASE_URL, NOYA_DATA_BASE_URL, NOYA_DOCS_BASE_URL, NOYA_TIMEZONE, WALLET_TYPE, NETWORK_ID, ADDRESS, OWNER_ADDRESS, PAYMASTER_URL, RPC_URL, and IDEMPOTENCY_KEY are no longer used.

• Removed: CDP_API_KEY_ID, CDP_API_KEY_SECRET, CDP_WALLET_SECRET, WALLET_TYPE, NETWORK_ID, ADDRESS, OWNER_ADDRESS, PAYMASTER_URL, RPC_URL, IDEMPOTENCY_KEY, NOYA_BASE_URL, NOYA_DATA_BASE_URL, NOYA_DOCS_BASE_URL, NOYA_TIMEZONE.
• Tool names unchanged for noya_* and noya_data_*.
• AgentKit tool rename: the cdp_ prefix is dropped (the wallet is now Privy-backed, not CDP-backed). Use the tool's native AgentKit name instead (e.g. cdp_transfer → transfer, cdp_get_wallet_details → get_wallet_details). Most tools now take an explicit chainId parameter.

If you need the legacy global CDP wallet model, pin to noya-agent-mcp@2 or use the legacy/v2 branch.

Development

npm install
npm run build
NOYA_API_KEY=noya_xxx node dist/index.js

License

MIT