NexusPress Draft MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXUSPRESS_API_URL | Yes | The URL of the NexusPress backend API. For local development use http://localhost:3001. | |
| NEXUSPRESS_ADMIN_TOKEN | Yes | The NexusPress admin JWT token. Retrieve from browser localStorage (nexus_admin_token). |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_publicationsA | List NexusPress publication sites available for drafting. |
| list_categoriesC | List categories for one NexusPress publication. |
| create_article_draftB | Create a completed article draft. If you have a temporary image URL (e.g. from DALL-E), pass it in temporaryCoverImageUrl to automatically upload and attach it as the permanent cover image. |
| update_article_draftC | Update an existing draft and automatically complete dependent fields. If you have a temporary image URL (e.g. from DALL-E), pass it in temporaryCoverImageUrl to automatically upload and attach it. |
| get_article_draftC | Get an existing NexusPress article draft for review. |
| check_draft_seoC | Run a local SEO check against draft fields before manual publishing. |
| upload_image_from_urlA | Upload an image from a temporary URL (e.g. from DALL-E) to Cloudinary to make it permanent. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource+action (list publications, list categories, get/create/update draft, SEO check, image upload), so an agent can tell them apart. The only mild overlap is upload_image_from_url, which duplicates image-attachment capabilities already embedded in create_article_draft and update_article_draft.
Predominantly a verb_noun snake_case pattern (list_publications, create_article_draft, update_article_draft, get_article_draft, upload_image_from_url). check_draft_seo deviates slightly with a verb_noun_noun ordering, but overall it's readable and predictable.
Seven tools is well-scoped for a draft-focused server, and each tool earns its place covering listing, drafting, review, validation, and asset handling.
The draft lifecycle (create, update, get) plus SEO check and image upload is solidly covered. Minor gaps exist: no listing of existing drafts and no delete_article_draft, though publishing is intentionally out of scope for a 'Draft' server.