notipo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_postsA | List all posts for your Notipo account. Returns title, status, WordPress URL, category, and timestamps. |
| get_postA | Get details of a specific post by ID, including status, WordPress URL, and category. |
| create_postA | Create a new blog post. Creates a Notion page and triggers sync to WordPress. The body should be markdown. Set publish=true to publish immediately, or leave false to create a draft. |
| direct_publishA | Publish a blog post directly to WordPress without Notion. Handles image uploads, Gutenberg conversion, featured image generation, and SEO metadata. Body must be markdown. Set publish=true to go live, false for draft. Use this instead of create_post when you don't need Notion. |
| update_postA | Update an existing post's content or properties in Notion, then re-sync to WordPress. Only provided fields are updated. |
| publish_postA | Publish a draft post to WordPress (make it live). |
| delete_postA | Delete a post from Notipo, WordPress, and reset the Notion page status. This cannot be undone. |
| list_categoriesA | List all WordPress categories synced to Notipo. Use these names when creating posts. |
| list_tagsA | List all WordPress tags synced to Notipo. Use these names when creating posts. |
| get_jobA | Check the status of a sync or publish job. Returns status (PENDING, RUNNING, COMPLETED, FAILED), progress steps, and any error message. |
| list_jobsA | List recent sync and publish jobs. Useful for monitoring pipeline activity. |
| get_settingsA | Get your Notipo account configuration: which services are connected (Notion, WordPress), current plan, feature settings, and trigger statuses. |
| sync_nowA | Trigger an immediate sync from Notion. Checks for any posts with trigger statuses and queues sync jobs. Pro plan only. Has a 15-second cooldown between calls. |
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 13 tools
Each tool targets a distinct operation, though create_post and direct_publish have overlapping purposes (both create posts) but their descriptions clearly differentiate the workflows (via Notion vs direct). Overall, an agent can easily distinguish them.
Most tools follow verb_noun pattern (create_post, list_posts, etc.), but 'direct_publish' uses an adjective+verb and 'sync_now' uses verb_adverb, which are minor inconsistencies. Overall, the naming is predictable.
With 13 tools, the server covers the full range of operations needed for managing posts between Notion and WordPress without being excessive. Each tool serves a clear purpose.
The tool set provides CRUD for posts, publishing, syncing, and monitoring jobs. However, it only lists categories and tags without create/update/delete capabilities, which is a minor gap.