Kraviona Admin MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_dashboard | Get Kraviona dashboard analytics — total posts, views, leads, messages, recent activity |
| get_posts | Get all blog posts (published + drafts) with pagination. Use status filter to get only published or draft posts. |
| get_single_post | Get full details of a single blog post by its slug |
| create_post | Create a new blog post with full SEO metadata, category, featured image, and content |
| update_post | Update an existing blog post by its ID — change title, content, status, SEO fields, category, image, etc. |
| delete_post | Permanently delete a blog post by its slug |
| publish_post | Publish a draft blog post (change status from draft to published) |
| unpublish_post | Unpublish a post (change status from published back to draft) |
| get_categories | Get all blog categories with their post counts and metadata |
| create_category | Create a new blog category with SEO metadata |
| update_category | Update an existing category by its slug |
| delete_category | Delete a blog category by its slug |
| get_comments | Get all blog comments (approved, pending, spam) |
| update_comment_status | Approve, reject, or mark a comment as spam |
| delete_comment | Permanently delete a comment by its ID |
| get_leads | Get all CRM leads with pagination |
| get_single_lead | Get full details of a single lead by its ID |
| update_lead_status | Update the status of a lead (e.g. new → contacted → qualified → closed) |
| delete_lead | Delete a lead by its ID |
| get_messages | Get all contact form messages with pagination |
| update_message_status | Mark a contact message as read or replied |
| delete_message | Delete a contact message by its ID |
| get_team | Get all team members |
| add_team_member | Add a new team member to the site |
| update_team_member | Update an existing team member's details by their ID |
| delete_team_member | Remove a team member by their ID |
| get_users | Get all admin users |
| update_user | Update an admin user's details or role |
| delete_user | Delete an admin user by their ID |
| get_site_settings | Get global site settings — site name, logo, SEO defaults, social links, contact info |
| update_site_settingsC | Update global site settings |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, the naming is trivially consistent.
A single tool for an admin server is too few; one would expect multiple tools for various settings and actions.
The tool only allows updating settings, but there is no way to read current settings or perform other admin tasks, leaving significant gaps.