Quickstart
Set up the Hyperterminal MCP server in 30 seconds
Get an API Key
You need a free API key. Sign up at hyperterminal.ai/developers to generate one instantly. See Reference for details on key format and limits.
Choose Your Transport
Pick the connection method that fits your setup. Both expose the exact same tools and resources.
| stdio | Streamable HTTP | |
|---|---|---|
| Setup | One-liner, zero config | Point at hosted URL + Bearer token |
| How it works | Client spawns server as a local child process | Client connects to hyperterminal.ai/api/mcp over HTTPS |
| Best for | Claude Code, Claude Desktop, Cursor, Windsurf, Cline, Codex CLI, Continue | Cloud agents, web apps, custom integrations |
| Network | Local only (stdin/stdout) | Works over any network |
Not sure? Start with stdio. It works with every client listed below and needs no extra infrastructure.
The client spawns the MCP server as a local child process via the @hyperterminal-ai/mcp-server npm package. Select your client below.
claude mcp add hyperterminal --env HYPERTERMINAL_API_KEY=ht_live_your_key -- npx -y @hyperterminal-ai/mcp-serverScope Options: Add these flags before the server name to change where it is installed:
--scope user: Makes it available across all your projects.--scope project: Shares it with your team via.mcp.json.- Default is
local(current project, private to you).
Management Commands:
claude mcp list # List all servers
claude mcp get hyperterminal # Get details
claude mcp remove hyperterminal # RemoveUse /mcp inside a Claude Code session to check server status.
Add the following to your claude_desktop_config.json file.
Configuration Paths:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
{
"mcpServers": {
"hyperterminal": {
"command": "npx",
"args": ["-y", "@hyperterminal-ai/mcp-server"],
"env": {
"HYPERTERMINAL_API_KEY": "ht_live_your_key_here"
}
}
}
}Warning
You must fully quit and relaunch Claude Desktop after editing the config. Changes are only read at startup.
Add the configuration below to .cursor/mcp.json (for the current project) or ~/.cursor/mcp.json (for global availability).
Alternatively, you can use the UI by going to Settings > MCP > Add new MCP server.
{
"mcpServers": {
"hyperterminal": {
"command": "npx",
"args": ["-y", "@hyperterminal-ai/mcp-server"],
"env": {
"HYPERTERMINAL_API_KEY": "ht_live_your_key_here"
}
}
}
}MCP tools are available in Cursor's Agent mode, not regular chat. You can use ${env:HYPERTERMINAL_API_KEY} in the JSON file to reference system environment variables instead of hardcoding your key.
Add the following to your mcp_config.json file. You can also access this via the UI: Cmd/Ctrl + , > Windsurf Settings > Plugins (MCP servers) > View raw config.
Configuration Paths:
| Platform | Path |
|---|---|
| macOS | ~/.codeium/windsurf/mcp_config.json |
| Windows | %USERPROFILE%\.codeium\windsurf\mcp_config.json |
| Linux | ~/.codeium/windsurf/mcp_config.json |
{
"mcpServers": {
"hyperterminal": {
"command": "npx",
"args": ["-y", "@hyperterminal-ai/mcp-server"],
"env": {
"HYPERTERMINAL_API_KEY": "ht_live_your_key_here"
}
}
}
}Use ${env:HYPERTERMINAL_API_KEY} to reference system environment variables. Make sure to click Refresh in the MCP Servers UI after updating.
codex mcp add hyperterminal --env HYPERTERMINAL_API_KEY=ht_live_your_key -- npx -y @hyperterminal-ai/mcp-serverOr manually edit your config file:
[mcp_servers.hyperterminal]
command = "npx"
args = ["-y", "@hyperterminal-ai/mcp-server"]
[mcp_servers.hyperterminal.env]
HYPERTERMINAL_API_KEY = "ht_live_your_key_here"Codex uses TOML, not JSON. Project-level configuration goes in .codex/config.toml at your project root. Use /mcp inside a Codex session to view active servers.
Create an mcpServers configuration file inside your project at .continue/mcpServers/hyperterminal.yaml:
name: Hyperterminal
version: 0.0.1
schema: v1
mcpServers:
- name: Hyperterminal AI News
type: stdio
command: npx
args:
- "-y"
- "@hyperterminal-ai/mcp-server"
env:
HYPERTERMINAL_API_KEY: ${{ secrets.HYPERTERMINAL_API_KEY }}Or drop a JSON config (in the same format as Claude Desktop) into .continue/mcpServers/. Continue auto-detects it.
MCP tools are only available in Agent mode. Secrets use the ${{ secrets.VAR }} syntax.
Open the Cline sidebar in VS Code, go to MCP Servers, and click Configure. This will open your cline_mcp_settings.json file.
{
"mcpServers": {
"hyperterminal": {
"command": "npx",
"args": ["-y", "@hyperterminal-ai/mcp-server"],
"env": {
"HYPERTERMINAL_API_KEY": "ht_live_your_key_here"
},
"alwaysAllow": [],
"disabled": false
}
}
}The alwaysAllow array takes tool names that should skip user confirmation. Leave it empty if you want to manually approve each tool call.
Connect directly to the hosted endpoint — no npm package, no local process. Your client talks to hyperterminal.ai/api/mcp over HTTPS with your API key as a Bearer token.
https://hyperterminal.ai/api/mcpSelect your client below.
{
"mcpServers": {
"hyperterminal": {
"type": "streamable-http",
"url": "https://hyperterminal.ai/api/mcp",
"headers": {
"Authorization": "Bearer ht_live_your_key_here"
}
}
}
}{
"mcpServers": {
"hyperterminal": {
"type": "streamable-http",
"url": "https://hyperterminal.ai/api/mcp",
"headers": {
"Authorization": "Bearer ht_live_your_key_here"
}
}
}
}import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
const client = new Client({ name: "my-app", version: "1.0.0" });
const transport = new StreamableHTTPClientTransport(
new URL("https://hyperterminal.ai/api/mcp"),
{
requestInit: {
headers: {
Authorization: "Bearer ht_live_your_key_here",
},
},
}
);
await client.connect(transport);Verify It Works
To make sure everything is connected, ask your agent:
"What small models have the best coding benchmarks right now?"
If it returns structured news results with impact levels, entity tags, and model names, you are good to go!
What can you build?
Here are a few things agents do well once connected:
- Morning briefing — pull the 5 highest-impact stories from the last 48 hours, filtered by topic or entity
- Competitive monitoring — ask what a specific company shipped this week, get structured events with source URLs
- Weekly strategic brief — get the digest: 94 events distilled to key developments with "why it matters" analysis, AGI tracking, and a podcast link
- Deep research — search a topic, get the top result, follow related stories by similarity score — three calls to build a full picture
See Use Cases for complete end-to-end workflows with real API responses.
Technical Details
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
HYPERTERMINAL_API_KEY | Yes | - | Your API key (starts with ht_live_) |
HYPERTERMINAL_BASE_URL | No | https://hyperterminal.ai | Override for testing |
Package Info
| Category | Details |
|---|---|
| npm Package | @hyperterminal-ai/mcp-server |
| Transports | stdio (npm package), Streamable HTTP (hosted) |
| License | MIT |