About MCP Client:
@pinax/mcp is a bridge client for connecting Claude Desktop and other stdio-compatible MCP clients to remote MCP servers. It forwards access to data from the Pinax Token API through the configured remote endpoint and access token.
Key features
- 01Bridges stdio clients to remote MCP
- 02Configurable remote URL
- 03JWT access-token authentication
- 04Verbose logging option
Use cases
- 01Connecting Claude Desktop to Pinax services
- 02Routing an MCP client to a remote server
- 03Supplying credentials through environment variables
MCP support
The client bridges stdio-compatible MCP clients to a remote MCP server over HTTP. The documented endpoint, https://mcp.pinax.network, exposes data provided by the Pinax Token API.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Client: @pinax/mcp
An MCP Client for connecting to MCP Server‐compatible services at https://app.pinax.network.
Usage
Usage: @pinax/mcp [options]
A bridge client for connecting Claude Desktop and other MCP-compatible clients to remote MCP servers.
Options:
-V, --version output the version number
--remote-url <string> Remote MCP server URL (env: REMOTE_URL)
--access-token <string> JWT Access Token (env: ACCESS_TOKEN)
-v, --verbose <boolean> Enable verbose logging (choices: "true", "false", default: false, env: VERBOSE)
-h, --help display help for command
Documentation: https://app.pinax.network/docs/guides/mcp
Endpoints
This MCP allows LLMs to access data provided by the Pinax Token API.
- Use
https://mcp.pinax.networkfor the MCP server (Streamable HTTP)
Authentication
- Sign in at https://app.pinax.network
- Go to Keys
- Copy your project key and generate a JWT Access Token
Configuration
Environment Variables (.env)
ACCESS_TOKEN=<your-jwt-token-from-app.pinax.network>
REMOTE_URL=https://mcp.pinax.network
Claude Desktop Configuration
Add to your Claude Desktop config file:
Location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Configuration:
{
"mcpServers": {
"pinax": {
"command": "npx",
"args": [
"@pinax/mcp",
"--remote-url",
"https://mcp.pinax.network",
"--access-token",
"YOUR_ACCESS_TOKEN_HERE"
]
}
}
}
Or using environment variables:
{
"mcpServers": {
"pinax": {
"command": "npx",
"args": ["@pinax/mcp"],
"env": {
"REMOTE_URL": "https://mcp.pinax.network",
"ACCESS_TOKEN": "YOUR_ACCESS_TOKEN_HERE"
}
}
}
}
Using with Bun (Development)
{
"mcpServers": {
"pinax": {
"command": "/path/to/bun",
"args": [
"run",
"/path/to/pinax-mcp/index.ts",
"--remote-url",
"http://localhost:8080/mcp",
"--access-token",
"YOUR_ACCESS_TOKEN_HERE",
"-v",
"true"
]
}
}
}
Supported Clients
This bridge works with any MCP client that supports stdio transport:
- Claude Desktop
- Cline
- Cursor
- Any other MCP-compatible application
Troubleshooting
Enable Verbose Logging
Add -v true to your command or set VERBOSE=true in your environment:
npx @pinax/mcp --remote-url https://example.com/mcp --access-token YOUR_TOKEN -v true
Common Issues
Connection Timeout:
- Verify your
ACCESS_TOKENis valid - Check that the
REMOTE_URLis correct and accessible
Authentication Failed:
- Generate a new access token at https://app.pinax.network/keys
- Ensure the token hasn't expired
Server Disconnected:
- Check Claude Desktop logs for detailed error messages
- Verify network connectivity to the remote server
Development
Install Dependencies
bun install
Run Locally
bun run index.ts --remote-url http://localhost:8080/mcp --access-token YOUR_TOKEN -v true
Build
bun build ./index.ts --outdir ./dist --target=node
Architecture
┌─────────────────┐ ┌──────────────┐ ┌─────────────────┐
│ Claude Desktop │◄──stdio─►│ MCP Bridge │◄──HTTP──►│ Remote MCP │
│ (or other │ │ Client │ │ Server │
│ MCP client) │ └──────────────┘ └─────────────────┘
└─────────────────┘
License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.