ThryxProtocol MCP Server

ThryxProtocol v3.1 — gasless AI agent launchpad on Base. 21 tools wrap thryx.fun HTTP API.

Local serverstdio

What is the ThryxProtocol MCP server?

ThryxProtocol MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. ThryxProtocol v3.1 — gasless AI agent launchpad on Base. 21 tools wrap thryx.fun HTTP API.

What you get

Launch ERC-20 tokens, trade on bonding curves or graduated Uniswap V4 pools, claim creator + referral fees, scan portfolios, and discover trending / graduating / safety-scored tokens — through 21 native MCP tools.

What the assistant can call

Once ThryxProtocol is connected, these are the calls the assistant has available:

  • thryx_balance — Your wallet balance + recommended next-action
  • thryx_portfolio — Full holdings scan with live PnL

Setting it up

The server ships on npm as @thryx/mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration and credentials

You will need 3 environment variables: THRYX_API_KEY, PRIVATE_KEY, THRYX_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

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. ThryxProtocol's toolset — thryx_balance, thryx_portfolio — is a fair guide to whether it matches your workflow. It is maintained by lordbasilaiassistant-sudo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the thryxprotocol mcp server does with a few real requests.

Available tools

ToolWhat it does
thryx_balanceYour wallet balance + recommended next-action.
thryx_portfolioFull holdings scan with live PnL.

How to install the ThryxProtocol MCP server

Or with an explicit key:

```json
{
  "mcpServers": {
    "thryx": {
      "command": "npx",
      "args": ["-y", "@thryx/mcp-server"],
      "env": { "THRYX_API_KEY": "thryx_..." }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
THRYX_API_KEYCredential the server authenticates with.Yes
PRIVATE_KEYCredential the server authenticates with.Yes
THRYX_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use ThryxProtocol to thryx balance.
  • Use ThryxProtocol to thryx portfolio.

Frequently asked questions

It connects ThryxProtocol to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (thryx_balance, thryx_portfolio) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with ThryxProtocol directly.