JPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JPI_BASE_URL | No | JPI API base URL | https://api.just-plan-it.com |
| JPI_API_TOKEN | Yes | Your JPI API token |
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 |
|---|---|
| jpi_api_infoA | Get information about the JPI API and available endpoints. Use this to understand what operations are available. |
| jpi_list_componentsB | List all components in the JPI system. Components are reusable building blocks that can be referenced by jobs. |
| jpi_create_componentC | Create a new component with tasks. |
| jpi_get_componentC | Get a specific component by its GUID. |
| jpi_update_componentC | Update an existing component. |
| jpi_delete_componentC | Delete a component by its GUID. |
| jpi_get_component_taskC | Get a specific task within a component. |
| jpi_add_component_taskC | Add a new task to a component. |
| jpi_update_component_taskC | Update a task within a component. |
| jpi_delete_component_taskC | Delete a task from a component. |
| jpi_list_jobsA | List all jobs in the JPI system with FULL task details. WARNING: Returns large payload. Use jpi_list_jobs_summary for job overviews or jpi_list_jobs_at_risk for risk analysis. |
| jpi_list_jobs_summaryA | List all jobs WITHOUT task details. Returns job metadata only (Name, DueDate, PlannedEnd, Status, etc.) with TaskCount. Use this for job overviews to reduce token usage (~80% smaller than jpi_list_jobs). |
| jpi_list_jobs_at_riskA | List jobs at risk of missing due dates. Returns only jobs where IsDueDateExceeded=true OR BufferLevel < threshold. Minimal fields for maximum token efficiency (~95% smaller than jpi_list_jobs). |
| jpi_create_jobC | Create a new job with tasks and scheduling information. |
| jpi_get_jobB | Get a specific job by its GUID. |
| jpi_update_jobC | Update an existing job. |
| jpi_delete_jobC | Delete a job by its GUID. |
| jpi_get_taskC | Get a specific task within a job. |
| jpi_add_taskC | Add a new task to a job. |
| jpi_update_taskC | Update a task within a job. |
| jpi_delete_taskC | Delete a task from a job. |
| jpi_get_jcrC | Get a Job Component Reference (JCR) - a reference to a component used in a job. |
| jpi_add_jcrB | Add a Job Component Reference to a job. |
| jpi_update_jcrC | Update a Job Component Reference. |
| jpi_delete_jcrC | Delete a Job Component Reference. |
| jpi_create_jobs_batchC | Create multiple jobs in a single batch operation. |
| jpi_update_jobs_batchC | Update multiple jobs in a single batch operation. |
| jpi_delete_jobs_batchC | Delete multiple jobs in a single batch operation. |
| jpi_add_tasks_batchC | Add multiple tasks to a job in a single batch operation. |
| jpi_update_tasks_batchC | Update multiple tasks within a job in a single batch operation. |
| jpi_delete_tasks_batchC | Delete multiple tasks from a job in a single batch operation. |
| jpi_add_jcrs_batchC | Add multiple Job Component References to a job in a single batch operation. |
| jpi_update_jcrs_batchC | Update multiple Job Component References in a single batch operation. |
| jpi_delete_jcrs_batchC | Delete multiple Job Component References in a single batch operation. |
| jpi_create_tasks_cross_jobsC | Create tasks across multiple jobs in a single batch operation. |
| jpi_update_tasks_cross_jobsB | Update tasks across multiple jobs in a single batch operation. |
| jpi_delete_tasks_cross_jobsC | Delete tasks across multiple jobs in a single batch operation. |
| jpi_list_templatesB | List all job templates. Templates are reusable job definitions. |
| jpi_create_templateC | Create a new job template. |
| jpi_get_templateB | Get a specific job template by its GUID. |
| jpi_update_templateC | Update an existing job template. |
| jpi_delete_templateC | Delete a job template by its GUID. |
| jpi_get_template_taskC | Get a specific task within a template. |
| jpi_add_template_taskC | Add a new task to a template. |
| jpi_update_template_taskC | Update a task within a template. |
| jpi_delete_template_taskC | Delete a task from a template. |
| jpi_get_tcrC | Get a Template Component Reference (TCR). |
| jpi_add_tcrC | Add a Template Component Reference to a template. |
| jpi_update_tcrC | Update a Template Component Reference. |
| jpi_delete_tcrC | Delete a Template Component Reference. |
| jpi_get_eventsC | Get JPI events (change log) created after a specific timestamp. |
| jpi_get_events_filteredC | Get JPI events filtered by event type. |
| jpi_list_resource_categoriesB | List all resource categories. Categories group related resource groups. |
| jpi_create_resource_categoryC | Create a new resource category. |
| jpi_get_resource_categoryB | Get a specific resource category by its GUID. |
| jpi_update_resource_categoryC | Update a resource category. |
| jpi_delete_resource_categoryC | Delete a resource category by its GUID. |
| jpi_list_resource_groupsB | List all resource groups. Groups organize resources that can perform similar work. |
| jpi_create_resource_groupC | Create a new resource group. |
| jpi_get_resource_groupB | Get a specific resource group by its GUID. |
| jpi_update_resource_groupC | Update a resource group. |
| jpi_delete_resource_groupC | Delete a resource group by its GUID. |
| jpi_list_resourcesB | List all resources. Resources are machines, workers, or other entities that perform work. |
| jpi_create_resourceC | Create a new resource. |
| jpi_get_resourceC | Get a specific resource by its GUID. |
| jpi_update_resourceC | Update a resource. |
| jpi_delete_resourceC | Delete a resource by its GUID. |
| jpi_get_settingsB | Get the JPI application settings including custom fields, planning configuration, and display options. |
| jpi_update_settingsC | Update JPI application 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 69 tools
The tools are well-differentiated by resource type (component, job, template, resource) and action (add, create, delete, get, list, update), with clear boundaries. However, some overlap exists between 'add' and 'create' operations (e.g., jpi_add_task vs. jpi_create_tasks_cross_jobs), which could cause minor confusion, but descriptions help clarify their distinct contexts.
Tool names follow a highly consistent verb_noun pattern with the 'jpi_' prefix throughout. Verbs like add, create, delete, get, list, and update are used predictably, and naming conventions (snake_case) are uniform across all 69 tools, making the set easy to navigate and understand.
With 69 tools, the count is excessive for typical MCP server purposes, leading to potential cognitive overload and inefficiency. While the domain (job planning and integration) is complex, the tool surface could be streamlined by reducing redundancy (e.g., multiple batch operations) without losing functionality.
The tool set provides comprehensive CRUD/lifecycle coverage for all core resources (components, jobs, templates, resources, categories, groups), including batch operations and settings management. No obvious gaps exist; agents can perform full workflows from creation to deletion with detailed querying and updates.