接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令？ 兩種安裝方式的差異
來自發布者
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 when you define agents.
The agentic server framework.
/agent/{name}The Quickstart walks through install, scaffold, and run, then optional MCP tool checks.
use + statement) or script-backed tools (handler).allow_all and api_key, plus custom plugins.curl -fsSL https://hyperterse.com/install | bash
hyperterse init
Generated starter structure:
.
├── .hyperterse
├── .agents/
│ └── skills/
│ ├── hyperterse-docs/
│ │ └── SKILL.md
│ └── hyperterse-agents/
│ └── SKILL.md
└── app/
└── tools/
└── hello-world/
├── config.terse
└── handler.ts
hyperterse start
With live reload:
hyperterse start --watch
curl http://localhost:8080/heartbeat
Expected response:
{ "success": true }
curl -s -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tools/list",
"id": 1
}' | jq
By design, Hyperterse exposes two transport-layer tools:
search - discover project tools by natural languageexecute - execute a project tool by namecurl -s -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "search",
"arguments": {
"query": "hello world greeting"
}
},
"id": 2
}' | jq
Search hits include name, description, relevance_score, and inputs.
curl -s -X POST http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "execute",
"arguments": {
"tool": "hello-world",
"inputs": { "name": "Hyperterse" }
}
},
"id": 3
}' | jq
hyperterse validate
hyperterse build -o dist
hyperterse serve dist/
my-project/
├── .hyperterse
├── app/
│ ├── adapters/
│ │ └── primary-db.terse
│ └── tools/
│ ├── get-user/
│ │ ├── config.terse
│ │ ├── input.ts
│ │ └── output.ts
│ └── get-weather/
│ ├── config.terse
│ └── handler.ts
└── package.json
.hyperterse)name: my-service
server:
port: 8080
log_level: 3
tools:
search:
limit: 10
cache:
enabled: true
ttl: 60
description: "Get user by ID"
use: primary-db
statement: |
SELECT id, name, email
FROM users
WHERE id = {{ inputs.user_id }}
inputs:
user_id:
type: int
auth:
plugin: api_key
policy:
value: "{{ env.API_KEY }}"
description: "Get weather by city"
handler: "./handler.ts"
inputs:
city:
type: string
auth:
plugin: allow_all
Supported input types:
stringintfloatbooleandatetimeEach tool must define exactly one execution mode:
use (adapter-backed), orhandler (script-backed)MCP — Streamable HTTP at /mcp (JSON-RPC 2.0): tools, prompts, resources, completion, subscriptions. See MCP transport.
A2A — JSON-RPC per agent at /agent/{agentName} (agent card, messaging, tasks, streaming). See A2A transport and Agents.
Execution pipeline:
Hyperterse implements the Model Context Protocol (MCP) specification 2025-11-25.
Compliance status by component:
Text content for tool results is supported; image, audio, and resource links are optional. Pagination applies when tools, prompts, or resources exceed typical small-to-medium counts.
{{ env.VAR_NAME }} for secrets and connection strings.{{ inputs.field }} statement substitution is textual; enforce strict input schemas and safe query patterns.llms.txt)See CONTRIBUTING.md and CODE_OF_CONDUCT.md.
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式，而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Hyperterse 透過 stdio 在本機執行。
上次檢查時間：2026-10-28。 The agentic server framework.