An MCP Client for connecting to MCP Server‐compatible services at https://app.pinax.network.
Most developer tooling work still happens through a UI a human drives. MCP Client: MCP server moves it into the conversation instead. An MCP Client for connecting to MCP Server‐compatible services at https://app.pinax.network.
A bridge client for connecting Claude Desktop and other MCP-compatible clients to remote MCP servers.
The server publishes 1 tool. What each one is for:
Build — The Build tool exposed by this serverConfiguration is passed through the environment: REMOTE_URL, ACCESS_TOKEN, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Client:'s toolset — Build — is a fair guide to whether it matches your workflow. It is maintained by pinax-network; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Build | The Build tool exposed by this server. |
Or using environment variables:
```json
{
"mcpServers": {
"pinax": {
"command": "npx",
"args": ["@pinax/mcp"],
"env": {
"REMOTE_URL": "https://mcp.pinax.network",
"ACCESS_TOKEN": "YOUR_ACCESS_TOKEN_HERE"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| REMOTE_URL | Endpoint or connection string the server talks to. | Yes |
| ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.