# Hyperterse — Agentic Server Framework (MCP + A2A)

> Deploy agents and MCP tools from one service. Exposes `/mcp` Streamable HTTP and A2A routes, with DB adapters and OpenTelemetry hooks.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
curl -fsSL https://hyperterse.com/install | bash
hyperterse init
hyperterse start

# Health check
curl http://localhost:8080/heartbeat
```

## Intro

Hyperterse is a server framework for running agents and MCP tools side-by-side, so you can deploy one process that serves tools, prompts, resources, and agent endpoints.

**Best for:** Teams building self-hosted tool servers, multi-agent backends, and MCP/A2A gateways

**Works with:** Linux/macOS; HTTP services; MCP clients that support Streamable HTTP; DB adapters (Postgres/MySQL/SQLite/Mongo/Redis)

**Setup time:** 10–20 minutes

### Key facts (verified)

- README describes exposing MCP Streamable HTTP at `/mcp` and agent routes like `/agent/{name}`.
- Lists DB adapters (PostgreSQL/MySQL/SQLite/MongoDB/Redis) and OpenTelemetry observability support (README).
- GitHub: 81 stars · 9 forks; pushed 2026-04-22 (GitHub API verified).

## 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)

<!-- Start of - Dont change this block -->
<div align="center">
  <picture>
    <img alt="Hyperterse — The agentic server framework." src="docs/assets/og.png" />
  </picture>
</div>
<br />
<div align="center">
  <h1>Hyperterse</h1>
</div>
<p align="center">
  <strong>The agentic server framework.</strong><br />
  <a href="https://hyperterse.com">Website</a>
  •
  <a href="https://docs.hyperterse.com">Documentation</a>
  •
  <a href="#quick-start">Quick Start</a>
  •
  <a href="#tool-examples">Examples</a>
  •
  <a href="https://github.com/hyperterse/hyperterse">GitHub</a>
</p>

---

<!-- End of - Dont change this block -->

**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](https://modelcontextprotocol.io/) Streamable HTTP at `/mcp` for tools, prompts, and resources; [A2A](https://github.com/a2aproject/a2a-go)-style agent routes live at `/agent/{name}` when you define agents.

## Where to start

- **Agents** — Declarative agents and A2A: [Agents overview](https://docs.hyperterse.com/agents/overview), [Agents quickstart](https://docs.hyperterse.com/agents/quickstart).
- **Tools** — Callable MCP tools (DB or scripts): [Tools](https://docs.hyperterse.com/concepts/tools), [Scripts](https://docs.hyperterse.com/concepts/scripts), [Adapters](https://docs.hyperterse.com/concepts/adapters).
- **Resources** — Static context for clients: [Resources](https://docs.hyperterse.com/concepts/resources).
- **Prompts** — Reusable prompt templates: [Prompts](https://docs.hyperterse.com/concepts/prompts).

The [Quickstart](https://docs.hyperterse.com/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](https://docs.hyperterse.com/concepts/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.

## Source & Thanks

> Source: https://github.com/hyperterse/hyperterse
> License: Apache-2.0
> GitHub stars: 81 · forks: 9

---

<!-- ZH -->

## 快速使用

```bash
curl -fsSL https://hyperterse.com/install | bash
hyperterse init
hyperterse start

# 健康检查
curl http://localhost:8080/heartbeat
```

## 简介

Hyperterse 是一个把 agents 与 MCP tools 放在同一服务里运行的框架：一次部署即可同时提供工具、提示词、资源与 agent endpoints。

**最适合：** 要自托管工具服务、多 Agent 后端、或搭建 MCP/A2A 网关的团队

**适配：** Linux/macOS；HTTP 服务；支持 Streamable HTTP 的 MCP 客户端；数据库适配（Postgres/MySQL/SQLite/Mongo/Redis）

**配置时间：** 10–20 分钟

### 关键事实（已验证）

- README 描述 MCP Streamable HTTP 端点为 `/mcp`，并支持 `/agent/{name}` 风格的 agent 路由。
- README 列出多种数据库适配（PostgreSQL/MySQL/SQLite/MongoDB/Redis）与 OpenTelemetry 可观测性支持。
- GitHub：81 stars · 9 forks；最近更新 2026-04-22（GitHub API 验证）。

## 正文

上手 Hyperterse 可以从“边界”开始：

- 先把它当成 MCP 工具网关：把高风险工具放到统一入口，并加上 auth / policy。
- 先接入一个数据库适配，只发布少量只读诊断工具。
- 等工具面稳定后，再扩展到多 Agent endpoints（A2A 路由）。


### README 原文节选（verbatim）

<!-- Start of - Dont change this block -->
<div align="center">
  <picture>
    <img alt="Hyperterse — The agentic server framework." src="docs/assets/og.png" />
  </picture>
</div>
<br />
<div align="center">
  <h1>Hyperterse</h1>
</div>
<p align="center">
  <strong>The agentic server framework.</strong><br />
  <a href="https://hyperterse.com">Website</a>
  •
  <a href="https://docs.hyperterse.com">Documentation</a>
  •
  <a href="#quick-start">Quick Start</a>
  •
  <a href="#tool-examples">Examples</a>
  •
  <a href="https://github.com/hyperterse/hyperterse">GitHub</a>
</p>

---

<!-- End of - Dont change this block -->

**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](https://modelcontextprotocol.io/) Streamable HTTP at `/mcp` for tools, prompts, and resources; [A2A](https://github.com/a2aproject/a2a-go)-style agent routes live at `/agent/{name}` when you define agents.

## Where to start

- **Agents** — Declarative agents and A2A: [Agents overview](https://docs.hyperterse.com/agents/overview), [Agents quickstart](https://docs.hyperterse.com/agents/quickstart).
- **Tools** — Callable MCP tools (DB or scripts): [Tools](https://docs.hyperterse.com/concepts/tools), [Scripts](https://docs.hyperterse.com/concepts/scripts), [Adapters](https://docs.hyperterse.com/concepts/adapters).
- **Resources** — Static context for clients: [Resources](https://docs.hyperterse.com/concepts/resources).
- **Prompts** — Reusable prompt templates: [Prompts](https://docs.hyperterse.com/concepts/prompts).

The [Quickstart](https://docs.hyperterse.com/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](https://docs.hyperterse.com/concepts/project-structure)).

### FAQ

**Hyperterse 只做 MCP 吗？**
答：README 同时描述了 MCP（tools/prompts/resources）与 A2A 风格的 agent routes，可在同一进程对外提供。

**客户端怎么调用工具？**
答：README 指向 `/mcp` 的 Streamable HTTP 作为 MCP 入口，可用于 tools/list 与工具调用。

**支持数据库吗？**
答：README 列出 PostgreSQL、MySQL、SQLite、MongoDB、Redis 等适配器。

## 来源与感谢

> Source: https://github.com/hyperterse/hyperterse
> License: Apache-2.0
> GitHub stars: 81 · forks: 9


---
Source: https://tokrepo.com/en/workflows/hyperterse-agentic-server-framework-mcp-a2a
Author: Agent Toolkit