Nexus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXUS_API_KEY | No | API key (overrides config file) | |
| NEXUS_API_URL | No | API base URL (overrides config file) |
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 |
|---|---|
| nexus_list_projectsB | List all projects in the organization with optional filtering by status or assignment |
| nexus_get_projectC | Get detailed information about a specific project |
| nexus_create_projectC | Create a new project in Nexus |
| nexus_update_projectC | Update a project's details including test credentials |
| nexus_update_project_statusC | Update a project's status |
| nexus_list_bugsC | Get all bugs/cards for a project with optional filtering |
| nexus_create_bugC | Create a new bug/issue card in a project |
| nexus_update_cardC | Update a card's status, assignee, or other fields |
| nexus_add_commentC | Add a comment to a card |
| nexus_list_templatesC | List available project templates |
| nexus_create_templateC | Create a new project template |
| nexus_list_milestonesC | List milestones with optional date range and type filtering |
| nexus_create_milestoneC | Create a new milestone |
| nexus_update_milestoneC | Update a milestone |
| nexus_update_milestone_taskC | Update a milestone subtask |
| nexus_list_conceptsC | List product concepts in the organization |
| nexus_get_conceptC | Get detailed information about a concept including PRD |
| nexus_create_conceptC | Create a new product concept |
| nexus_update_conceptC | Update a concept |
| nexus_promote_conceptC | Promote a concept to a full project |
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 20 tools
Most tools have distinct purposes targeting different resources (projects, concepts, bugs, milestones, templates), but there is some potential overlap between nexus_update_card and nexus_update_project_status since both could involve status changes. The descriptions clarify that nexus_update_card focuses on individual cards while nexus_update_project_status handles overall project status, but agents might initially confuse them.
All tools follow a consistent 'nexus_verb_noun' pattern with snake_case throughout. The verbs (add, create, get, list, promote, update) are used predictably across different resource types, making the naming scheme highly uniform and easy to understand.
20 tools is slightly high but reasonable for a project management system covering multiple resource types (projects, concepts, bugs, milestones, templates). Each tool appears to serve a specific function without obvious redundancy, though the count borders on being heavy for some agent workflows.
The toolset provides comprehensive CRUD/lifecycle coverage for the project management domain. It includes creation (create_*), retrieval (get_*, list_*), updates (update_*), and specialized operations like promote_concept. There are no apparent gaps that would prevent agents from managing the full lifecycle of projects, concepts, bugs, and milestones.