MCP.so
ログイン

MCP Client

@pinax-network

基本情報

カテゴリ

その他

ライセンス

Apache-2.0

トランスポート

stdio

作者

pinax-network

MCP Client について

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

MCP Client の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

MCP Client のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

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

よくある質問

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.

コメント

「その他」の他のコンテンツ