Main

A practical way to adopt Hyperterse is to start from the boundary:

• Use it as an MCP tool gateway that wraps your “dangerous” tooling behind auth and policies.
• Add one database adapter and publish a small set of read-only diagnostics first.
• Only then expand into multi-agent endpoints (A2A routes) once your tool surface is stable.

README excerpt (verbatim)

The agentic server framework.
Website • Documentation • Quick Start • Examples • GitHub

Hyperterse is an agentic server framework: one build ships agents (A2A), tools (MCP), prompts, resources, database adapters, auth, caching, and observability from a single process. You declare surfaces in config; the compiler validates and bundles them. Clients use MCP Streamable HTTP at /mcp for tools, prompts, and resources; A2A-style agent routes live at /agent/{name} when you define agents.

Where to start

• Agents — Declarative agents and A2A: Agents overview, Agents quickstart.
• Tools — Callable MCP tools (DB or scripts): Tools, Scripts, Adapters.
• Resources — Static context for clients: Resources.
• Prompts — Reusable prompt templates: Prompts.

The Quickstart walks through install, scaffold, and run, then optional MCP tool checks.

What Hyperterse is for

• Running agents alongside MCP tools, prompts, and resources in one deployable service
• Exposing database queries and custom logic as MCP tools with declarative config
• Production Streamable HTTP for MCP and A2A routes for agents
• TypeScript handlers and transforms where config alone is not enough

Core capabilities

• Agents: declarative configs, tool-access policies, multi-provider models, per-agent A2A HTTP.
• Filesystem discovery: one MCP tool per tool definition; prompts and resources follow the same discover-and-compile model (see Project structure).

FAQ

Q: Is Hyperterse only for MCP? A: README describes both MCP tools/prompts/resources and agent routes (A2A-style) served from one process.

Q: How do clients call tools? A: README points to MCP Streamable HTTP at /mcp for tools/list and tool calls.

Q: Does it support databases? A: README lists adapters for PostgreSQL, MySQL, SQLite, MongoDB, and Redis.