lontar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LONTAR_API_URL | Yes | API base URL, e.g. https://example.com/api | |
| LONTAR_API_TOKEN | No | Laravel Sanctum bearer token (required for write operations) |
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 published blog posts (paginated). Returns title, slug, excerpt, and published_at for each post. |
| get_postA | Get a single published post by slug. Returns full post data including body and rendered_body (HTML). |
| list_draftsA | List draft posts (paginated). Requires LONTAR_API_TOKEN. Returns title, slug, excerpt, and created_at. |
| create_postA | Create a new blog post. Requires LONTAR_API_TOKEN. Slug is auto-generated from the title. Omit published_at to create a draft. |
| update_postA | Update an existing post by slug. Requires LONTAR_API_TOKEN. Only provided fields are changed. |
| delete_postA | Permanently delete a post by slug. Requires LONTAR_API_TOKEN. |
| publish_postB | Publish a draft post by setting published_at to now. Requires LONTAR_API_TOKEN. |
| unpublish_postA | Unpublish a post by clearing published_at. Requires LONTAR_API_TOKEN. |
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 8 tools
Each tool targets a distinct action on posts or drafts: create, delete, get, list drafts, list published, publish, unpublish, update. No overlapping purposes.
All tool names follow a consistent verb_noun pattern (e.g., create_post, list_drafts, publish_post), making predictions easy.
8 tools cover the core blog post lifecycle without being excessive or too sparse. Each tool serves a clear role.
Covers full CRUD plus draft/publish state management. Minor gap: no search or filtering tools, but core workflow is complete.