MCP.so
Sign In

MCP Client

@pinax-network

Basic information

Category

Other

License

Apache-2.0

Transports

stdio

Author

pinax-network

About MCP Client

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

MCP Client 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"
      ]
    }
  }
}

MCP Client tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

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

Frequently asked questions

1

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.

2

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.

3

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`).

4

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.

5

Does MCP Client work with clients other than Claude Desktop?

Yes. It is compatible with any MCP client that supports stdio transport, including Cline and Cursor.

Comments

More Other MCP servers