AINative Strapi MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRAPI_URL | Yes | Your Strapi instance URL (e.g., https://cms.example.com) | |
| STRAPI_ADMIN_EMAIL | Yes | Admin email for authentication | |
| STRAPI_ADMIN_PASSWORD | Yes | Admin password for authentication |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| strapi_create_blog_postC | Create a new blog post in Strapi CMS with markdown content |
| strapi_list_blog_postsB | List all blog posts with advanced filtering, sorting, and pagination |
| strapi_get_blog_postB | Get a specific blog post by document ID |
| strapi_update_blog_postC | Update an existing blog post |
| strapi_publish_blog_postC | Publish or unpublish a blog post |
| strapi_list_authorsB | List all authors |
| strapi_list_categoriesB | List all categories |
| strapi_list_tagsB | List all tags |
| strapi_create_tutorialC | Create a new tutorial with step-by-step content in markdown |
| strapi_list_tutorialsC | List all tutorials with filtering and pagination |
| strapi_get_tutorialC | Get a specific tutorial by document ID |
| strapi_update_tutorialC | Update an existing tutorial |
| strapi_publish_tutorialC | Publish or unpublish a tutorial |
| strapi_create_eventC | Create a new event (webinar, workshop, meetup, conference) |
| strapi_list_eventsB | List all events with filtering and pagination |
| strapi_get_eventB | Get a specific event by document ID |
| strapi_update_eventC | Update an existing event |
| strapi_publish_eventC | Publish or unpublish an event |
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 18 tools
Every tool has a clearly distinct purpose based on resource type (blog_post, event, tutorial, author, category, tag) and action (create, get, list, publish, update), with no overlapping functionality. The descriptions reinforce this separation, making tool selection unambiguous.
All tools follow a strict and predictable pattern: 'strapi_' prefix, then verb (create, get, list, publish, update), then noun (e.g., blog_post, event, tutorial). This consistency is maintained across all 18 tools, making the set highly readable and systematic.
With 18 tools, the count is slightly high but reasonable for a CMS server covering multiple content types (blog posts, events, tutorials) and supporting full CRUD operations plus listing and publishing. It feels comprehensive rather than bloated, though it could be streamlined by reducing redundancy in some list operations.
The tool set provides complete CRUD and lifecycle coverage for the core content types (blog posts, events, tutorials), including create, get, update, list, and publish/unpublish actions. It also includes auxiliary resources like authors, categories, and tags, leaving no obvious gaps for typical CMS workflows.