hypertxt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYPERTXT_API_KEY | Yes | Your Hypertxt API key, created in Hypertxt → Account → Automation. | |
| HYPERTXT_API_URL | No | Base URL for Hypertxt API. Default is https://app.hypertxt.ai. | https://app.hypertxt.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| account_statusA | Show the account plan, subscription status, and remaining generation credits. |
| list_projectsB | List the Hypertxt projects available to this API key. |
| list_workflowsC | List article templates, optionally restricted to one project. |
| list_articlesA | List generated articles, optionally filtered by project and lifecycle status. |
| get_articleB | Get an article's metadata, state, outline, and full content. |
| generate_articleC | Spend one available credit and queue an article after user approval. |
| change_article_stateC | Record an approved editorial state change after inspecting the article. |
| export_articleA | Export an article as Markdown, HTML, or plain text. |
| list_integrationsC | List connected WordPress, Ghost, or webhook publishing destinations. |
| publish_articleC | Create a destination draft or publish live after explicit user approval. |
| list_gsc_connectionsB | List Google Search Console properties connected to a project. |
| query_gscC | Query synchronized or exact-window live GSC performance. |
| sync_gscC | Queue a durable refresh of one GSC property after user approval. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| account_status_resource | Read plan and credit status as a JSON MCP resource. |
TDQS
Scored across 13 tools
Every tool addresses a unique function: account info, GSC operations, project listing, workflow templates, article CRUD (except delete), export, integration listing, and publishing. No two tools have overlapping purposes.
Most tools follow a clean verb_noun pattern (list_*, get_*, generate_*, etc.). The only exception is 'account_status', which is noun_noun. This minor inconsistency breaks the pattern slightly but does not cause confusion.
13 tools is well-scoped for a content generation and SEO platform. Each tool earns its place, covering account management, project navigation, GSC integration, article lifecycle, and publishing without unnecessary bloat.
Core operations are present: generate, read, change state, export, and publish articles. However, there is no tool to delete articles or update their content after generation, and integration management is limited to listing only. These gaps may require workarounds.