Treg.to logo

Treg.to

Routes agents to a catalog of external tools and team-owned APIs through one MCP endpoint and token.

Install Treg.to

Run the project’s own setup commands, in order.

Setup steps from the project

treg.to installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Install
    curl -fsSL https://treg.to/install.sh | sh
    
  2. 2. Sign in
    treg login
    

Overview

treg.to MCP server connects agents to a catalog of external endpoints and to tools registered by a team. Agents can search by task, inspect inputs and pricing, then call endpoints through one hosted MCP URL and token. Credentials are injected server-side, while team-owned APIs, OAuth connections, CLIs, and skills can be shared without exposing their secrets. Reach for treg.to when an agent needs access to varied data, enrichment, scraping, social, advertising, or media-generation tools without separate provider accounts.

Use cases

  • Search for a data or enrichment endpoint by task
  • Call provider APIs without managing separate provider accounts
  • Share team credentials and CLIs with multiple agents
  • Run research workflows for leads, recruiting, or web access

Key features

  • Task-based catalog search
  • Server-side credential injection
  • Team-owned API, OAuth, CLI, and skill registration
  • Parameter and price inspection before calls
  • Hosted MCP endpoints
  • CLI-based balance and credential health checks

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

47/47 checks healthy over the last 68d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 27d ago via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars8kStargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Treg.to works

What treg.to MCP server does

treg.to provides an aggregation layer for agent tools and data. Its catalog groups external endpoints by the job they perform, including backlink research, SEO and rank tracking, social and trend analysis, people and company enrichment, advertising, scraping, and image, video, or audio generation. Agents can search by task instead of starting with a known vendor.

The same registry can expose tools belonging to a team. These may be paid APIs, OAuth connections, vendor command-line programs, or workflow skills defined with a SKILL.md file. A team can register these resources so teammates' agents can use them without receiving the underlying credentials.

How it works

Requests use one treg token, sent in the X-Treg-Token header. The proxy forwards calls to upstream services and adds authentication on the server side; it does not create a separate model of each upstream API. When a team has registered its own provider tool or secret, that credential takes precedence over treg's catalog credential and calls are not metered through the catalog balance.

The command-line workflow illustrates the registry's main operations:

  • treg catalog search finds tools by description of the desired task.
  • treg catalog get <id> shows a tool's declared parameters, price, and example response.
  • treg call <id> invokes a catalog or registered tool.
  • treg balance reports call spending.
  • treg tool ls lists tools shared with the team.
  • treg health checks credential status.

Catalog tools can be called with query parameters, headers, and request bodies. Tools marked strict_query reject undeclared or repeated query parameters, unsupported values, and request bodies that do not meet their declared contract.

Setup and configuration

Install the CLI and sign in through the hosted registry:

Terminal
curl -fsSL https://treg.to/install.sh | sh
treg login

GitHub is the default sign-in method; email one-time codes and token-based login for agents or CI are also supported. After authentication, the same token is used across tools. The guided treg onboard command is available instead of following the individual quickstart steps.

Claude Code users can install the marketplace plugin with /plugin marketplace add superdesigndev/treg followed by /plugin install treg@treg. The plugin adds the skill and tools; sign-in is completed from the MCP interface. Other public workflow skills can be added with the skills CLI or the treg bootstrap command.

The hosted MCP surfaces are available at https://treg.to/mcp/ and, for the Claude Connectors Directory, https://treg.to/mcp/v2/. The v2 connector exposes curated catalog endpoints and separates read and write calls. treg.to can also be self-hosted.

Tools and capabilities

  • Search a catalog of external tools by task or provider.
  • Inspect declared parameters, pricing, and example responses before calling.
  • Relay requests using catalog credentials or a team's own credentials.
  • Register and share APIs, OAuth connections, vendor CLIs, and skills.
  • Run workflow skills such as web access, lead-signal research, recruiting, and AI UGC creation.
  • Call media and data services through the CLI, including binary responses redirected to files.

Limitations and notes

The proxy relays upstream services rather than normalizing their interfaces, so callers work with each tool's declared request shape. Catalog coverage and behavior depend on the available endpoints and their provider routes. The Claude connector's v2 surface is limited to curated catalog endpoints and excludes image, video, and audio generation; the regular MCP surface also supports team-owned tools and imported skills.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Treg.to

treg.to is an MCP server that connects agents to a catalog of external tool and data endpoints plus team-registered APIs, OAuth connections, CLIs, and skills. Its main tools search the catalog, inspect tool inputs, invoke endpoints, and check balances and credential health.

Install the CLI with `curl -fsSL https://treg.to/install.sh | sh`, then run `treg login`. The installer points the CLI at the hosted registry, and Claude Code users can instead install the treg marketplace plugin.

treg.to authenticates calls with one token sent in the `X-Treg-Token` header. Credentials for catalog providers or team-owned tools are injected server-side, so agents do not need to hold the upstream secrets.

Yes, a team's registered tool or stored provider secret takes precedence over treg's catalog credential. Calls using a team's own key are relayed to the upstream provider and are not metered through treg's catalog balance.

Yes, treg.to provides a Claude Code marketplace plugin. Add the `superdesigndev/treg` marketplace, install `treg@treg`, then use `/mcp` to select treg and sign in.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTreg.to AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/treg-to?style=directory)](https://allmcps.com/mcp/treg-to)
HTML Embed
<a href="https://allmcps.com/mcp/treg-to"><img src="https://allmcps.com/api/badge/treg-to?style=directory" alt="Treg.to on AllMCPs" /></a>