MCP Client:

Name: MCP Client:
Author: pinax-network

@pinax-network

Repository

About MCP Client:

An MCP Client for connecting to MCP Server‐compatible services at https://app.pinax.network.

#mcp #client #api

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "pinax-mcp": {
      "command": "npx",
      "args": [
        "@pinax/mcp",
        "--remote-url",
        "https://example.com/mcp",
        "--access-token",
        "YOUR_TOKEN",
        "-v",
        "true"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Client?

It is a bridge client that connects MCP‑compatible applications (such as Claude Desktop, Cline, or Cursor) to remote MCP servers. It is specifically designed to access data from the Pinax Token API hosted at https://app.pinax.network.

How to use MCP Client?

Install and run via npx @pinax/mcp, providing a remote server URL and a JWT access token. You can configure it in Claude Desktop’s configuration file (claude_desktop_config.json) using either command‑line arguments or environment variables.

Key features of MCP Client

Connects MCP clients to remote MCP servers via stdio transport
Uses JWT access tokens for authentication
Provides verbose logging for troubleshooting (option -v true)
Works with any MCP‑compatible application
Allows local development with Bun

Use cases of MCP Client

Querying Pinax Token API data from Claude Desktop
Connecting Cline or Cursor to a remote MCP server
Developing and testing MCP integrations locally using Bun
Debugging connection issues with verbose logging

FAQ from MCP Client

What does MCP Client do?

It acts as a bridge, relaying communication between a local MCP client (e.g., Claude Desktop) and a remote MCP server using the stdio transport.

How do I authenticate with the remote server?

Provide a JWT access token via the --access-token option or the ACCESS_TOKEN environment variable. Tokens are generated from the Pinax dashboard at https://app.pinax.network/keys.

Which transport does MCP Client use?

The local side uses stdio transport; the bridge communicates with the remote server over HTTP (Streamable HTTP on https://mcp.pinax.network).

Where can I find logs if something goes wrong?

Enable verbose logging with -v true. Common issues (timeout, auth failure, disconnect) are documented in the Troubleshooting section; check Claude Desktop logs for detailed error messages.