agent-nexus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOC_EXCHANGE_HOST | No | Server bind host | 0.0.0.0 |
| DOC_EXCHANGE_PORT | No | Server port | 10086 |
| DOC_EXCHANGE_DB_URL | No | Database URL | sqlite:///doc_exchange.db |
| DOC_EXCHANGE_DOCS_ROOT | No | Workspace root (docs live under {root}/{space_id}/docs/) | ./workspace |
| DOC_EXCHANGE_DEFAULT_SPACE_ID | No | Default space for FileWatcher | default |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| push_documentC | Push a new document version to the exchange center. |
| patch_documentA | Apply a unified diff patch to an existing document, producing a new version. Use instead of push_document when only part of the document changed — avoids sending the full content and works around tool-call payload size limits. patch must be in unified diff format (output of difflib.unified_diff). base_version must match the current latest version; if not, returns PATCH_BASE_MISMATCH — call get_document to fetch latest and regenerate. |
| get_documentB | Retrieve a document (latest or specific version). |
| get_my_updates_with_contextA | Return all unread notifications with diff and full latest document content. One call gives everything needed to understand what changed and act on it. After processing, call ack_update for each update_id to mark as read. |
| get_my_updatesA | Return all unread notifications for the given project. |
| ack_updateC | Acknowledge (mark as read) a notification. |
| get_my_tasksC | Return all pending/in-progress tasks for the given project. |
| get_configB | Return the config document for the given project and stage. |
| generate_steering_fileB | Generate the content for a .kiro/steering/doc-exchange.md Steering file. The sub-project Kiro should create this file to enable automatic doc-update checks. |
| get_project_id_by_nameB | Look up a sub-project's project_id by its human-readable name. |
| add_subscriptionB | Add a subscription rule. Provide target_doc_id for exact doc or target_doc_type for all docs of that type. |
| create_spaceC | Create a new Project Space. Returns the space_id needed for registering projects. |
| register_projectC | Register a new sub-project in the given project space. type: development | testing | ops | infra | shared | ... stage: design | development | testing | deployment | upgrade |
| list_projectsC | List all sub-projects in the given project space. |
| publish_draftC | Confirm a draft document version, publishing it and triggering notifications. |
| list_documentsA | List all documents belonging to the given sub-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 16 tools
Each tool has a clearly distinct purpose. The only potential overlap (get_my_updates vs. get_my_updates_with_context) is resolved by the latter being a superset with explicit context. push_document and patch_document are differentiated by full vs. partial updates.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_space, list_documents, ack_update). Minor abbreviation like 'ack' is acceptable and does not break consistency.
16 tools cover spaces, projects, documents, notifications, subscriptions, and tasks. This is well-scoped for a project/document management server, not too many or too few.
The tool surface covers core create and read operations but lacks update and delete for projects, documents, subscriptions, and tasks. Missing create tasks and delete operations for multiple resources are notable gaps.