Tools built for agents.

Small, functional tools. Explicit schemas. Structured results. Connect once to use every published tool, or connect to an individual tool.

Connect with MCP

{
  "mcpServers": {
    "super-agent-tools": {
      "url": "https://app.getsupers.com/sites/agent-tools/mcp"
    }
  }
}
Streamable HTTP · No API key · Stateless

Use this URL in any client supporting remote Streamable HTTP MCP. Calls return structured JSON; inputs are processed without persistence.

Available tools

A directory exposes explicit tool contracts

Read the explanation

This directory presents fifty saved tool entries and one hub MCP configuration. Individual tool pages also expose their own connection URLs and documented schemas. Connecting is a client action; reading or copying configuration does not execute a tool. This local explainer describes the saved page, not the current remote service inventory, authentication behavior or availability. The saved directory labels eleven entries functional, ten collaboration, ten three dimensional, nine math, nine media and one data. These counts total fifty. Labels are catalog organization, not interchangeable input types. For example, a text span uses Unicode positions, while a WAV trimmer uses audio frames. A tool consumer must read each exact schema and notes before choosing an operation. The page describes small tools with structured results. Tool-specific pages provide the argument shape and HTTP alternative. Geometry, math and media tools operate on different supplied data, and returned artifacts or validation errors must be inspected. This directory does not provide a live execution console. No HTTP or MCP requests are sent by this local verification, so remote parity and real public functionality remain unverified.

Agent Tools Hub: Streamable MCP Directory Architecture

How do clients connect to and discover tools using the Model Context Protocol (MCP) server configuration listed on this page?

This hub catalogs functional agent tools across domains such as collaboration, 3D math, media, and data manipulation. The page provides an MCP server configuration snippet pointing to a streamable HTTP endpoint. When integrated into an MCP-compatible host or orchestrator, the client establishes an HTTP connection to query advertised tool schemas and execute individual operations statelessly without persistent session storage.

This hub page is an index and configuration catalog; it does not execute remote agent tool calls directly within this overview page. Each cataloged tool operates with its own specific input schemas, validation constraints, and deterministic outputs on its respective endpoint.

Try a worked example

To configure an agent client, paste the provided JSON snippet into the client's MCP configuration settings. The client connects to the endpoint https://app.getsupers.com/sites/agent-tools/mcp, requests available tool schemas (for example, reading parameter expectations for tools like the Task graph planner or Mesh transform), and invokes specific tool procedures using structured JSON payloads.

Directory and Protocol Role

The hub groups tools by category (such as collaboration, 3d, math, media, and functional) and points to a single streamable MCP endpoint. Agent environments parse this configuration to identify remote procedure endpoints, inspect parameter schemas, and receive structured JSON responses.

Stateless Invocation

The advertised streamable HTTP MCP connection operates without requiring API keys or retaining state between requests. Input parameters must contain complete information for each execution.