Trinity-MCP

Provides a token-protected MCP server to list and call tools via an MCP client.

other

0

GitHub Stars

other

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "kklab-com-trinity-mcp": {
      "command": "./trinity-mcp",
      "args": [
        "-t",
        "<token>"
      ]
    }
  }
}

Trinity-MCP enables you to run a local MCP server that exposes tool management through a token-protected interface. It lets you initialize, list available tools, and execute tools remotely via the MCP protocol, making it easy to integrate with MCP clients and automation workflows.

How to use

Start the server with the provided token to enable tool access and management through your MCP client. Once running, you can initialize your client session, list the available tools, and call specific tools by name with the required arguments. Interact through your MCP client to perform actions such as querying which tools exist, preparing inputs, and invoking tool endpoints.

Typical usage patterns include starting the server, creating an initialization context, discovering available tools, and invoking a selected tool with its required parameters. Your MCP client should handle responses and errors according to the MCP protocol, and you should manage the lifecycle of the session as you perform sequences of tool calls.

How to install

# prerequisites: a Unix-like environment with a compatible shell
# ensure you have execute permissions for the Trinity MCP binary

# Step 1: obtain the Trinity-MCP executable (trinity-mcp)
# Step 2: give execute permission if needed
chmod +x ./trinity-mcp

# Step 3: run the server with your access token
./trinity-mcp -t <token>

Note: Replace <token> with your actual MCP access token. The server will start and listen for MCP client connections using the provided token for authentication.

## Additional notes

Tools you can access via this MCP server are exposed as endpoints that you can list and invoke through your MCP client. You will typically first list available tools, then call a specific tool by its name and supply the required arguments.

## Available tools

### tools/list

Lists all available MCP tools exposed by the server, allowing you to discover what actions you can perform.

### tools/call

Invokes a specific tool by name with the required arguments, enabling execution of tool logic through the MCP interface.