Lific
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 |
|---|---|
| add_commentA | Add a comment to an issue (LIF-42) or page (LIF-DOC-3; DOC-3 for workspace pages). The author is the authenticated user. |
| bulk_updateA | Apply field changes to matching issues in one call. At most 500 matching issues are selected; narrow filters when more matches exist. Returns the number of issues updated. |
| create_issueC | Create a new issue in a project |
| create_pageC | Create a new page in a project |
| create_planA | Create a nestable step-by-step plan that survives outside the context window. Steps can mirror issues via 'issue': closing the issue completes the step and vice versa. |
| deleteA | Delete any resource by type and identifier. Types: issue, page, plan, project, module, label, folder. |
| delete_commentA | Delete a comment by id. Author or admin only. |
| edit_commentA | Edit a comment's content by id. Author or admin only; @mentions re-resolve. |
| edit_issueA | Edit an issue by replacing an exact string. Targets the description by default; pass field='title' for the title. Fails if old_string is missing or ambiguous (unless replace_all=true). Cheaper than update_issue for small changes. |
| edit_pageA | Edit a page by exact string replacement; same contract as edit_issue. Targets the content by default; pass field='title' for the title. |
| edit_plan_stepA | Edit a plan step's text by exact string replacement; same contract as edit_issue. Targets description by default; pass field='title'. |
| exportA | Export as markdown: an issue (PRO-42), a page (PRO-DOC-3), or a whole project (PRO). Issues and pages return the markdown; projects return the exported file paths. |
| get_activityA | Read the audit log: who changed what, when, and through which door (web UI, MCP, API, CLI). Takes an issue, page, or project ID; project scope covers the whole feed. Newest-first with old and new values. |
| get_boardA | Board view of issues grouped by status (default), priority, or module. Done/cancelled are count-only stubs unless include_closed=true. |
| get_issueA | Get an issue by ID (e.g. LIF-1): full details plus the last 3 comments by default. |
| get_pageA | Get a page by identifier (e.g. LIF-DOC-1). Returns full content. |
| get_planA | Rehydrate a plan's full step tree (e.g. LIF-PLAN-3) when resuming work. Step lines show the #id used by edit_plan_step and update_plan_step, done state, and linked issues. |
| link_issuesA | Link two issues with a relation: blocks, relates_to, or duplicate |
| list_commentsB | List comments on an issue (LIF-42) or page (LIF-DOC-3; DOC-3 for workspace pages). |
| list_issuesC | List issues for a project. workable=true gives issues with no blockers, blocked=true for issues with at least one blocker. |
| list_resourcesB | List resources by type: project, module, label, folder, page, issue, or plan. Most types need a project identifier. |
| manage_resourceA | Create or update a project, module, label, or folder. Create project requires name and identifier; project update requires project=; module/label/folder create requires project and name; module/label/folder update requires project and current_name. Use delete for deletion. |
| searchB | Search across all issues, pages, and comments by text |
| unlink_issuesA | Remove a relation between two issues |
| update_issueA | Update an existing issue by identifier. Only provided fields are changed. |
| update_pageB | Update a page by identifier. Only provided fields are changed. |
| update_plan_stepA | Mutate a plan or one step. With step_id: step CRUD, done toggling, attach/detach issue (linked issues sync state). Without step_id: update the plan itself; plan status never closes the anchor issue. Returns a delta. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/VoidNullable/lific'
If you have feedback or need assistance with the MCP directory API, please join our Discord server