mcp-cosense
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COSENSE_HOME | No | Home containing .cosense credentials | current home |
| COSENSE_MCP_HOST | No | HTTP listen address; Docker sets 0.0.0.0 | 127.0.0.1 |
| COSENSE_MCP_PORT | No | HTTP listen port | 8798 |
| COSENSE_CLI_CONCURRENCY | No | Maximum concurrent CLI processes | 4 |
| COSENSE_ALLOWED_PROJECTS | Yes | Comma-separated exact project URLs; empty disables access | |
| COSENSE_MCP_ALLOWED_HOSTS | No | Accepted HTTP Host headers | localhost values |
| COSENSE_CLI_TIMEOUT_SECONDS | No | Per-command timeout | 120 |
| COSENSE_CLI_MAX_OUTPUT_BYTES | No | Per-stream output limit | 4194304 |
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 |
|---|---|
| browse_pageB | Read one Cosense page in an agent-friendly format with metadata and links. |
| browse_related_pagesA | List one-hop and two-hop pages related to a Cosense page. |
| read_pageA | Read structured page JSON, including page ID and line IDs used for edits. |
| search_full_textA | Search complete Cosense page text with AND or OR matching. |
| search_vectorB | Semantically search Cosense titles and link notation. |
| preview_editA | Preview an explicitly requested edit without changing the page. First call read_page and use its top-level page ID and lines[].id values. Inspect the returned complete post-edit page before calling submit_edit. |
| preview_new_pageA | Preview creation of a new page without changing Cosense. Use this only for an explicitly requested write. The title and each item in lines represent one Cosense line. Inspect the preview before submitting it. |
| submit_editA | Commit one inspected Cosense edit preview. This mutates Cosense. Call it only for the same explicit user write request that produced the preview. Never retry an ambiguous result before read_page confirms whether the intended change already landed. |
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
browse_page and read_page both read a single page, but their purposes are differentiated by output format and edit intent. The search tools, related-pages tool, and preview/submit tools are clearly distinct, so an agent can generally select correctly.
All tool names follow a consistent snake_case verb-first pattern such as browse_, read_, search_, preview_, and submit_. The naming conventions are uniform and predictable across the entire set.
Eight tools is a well-scoped count for a Cosense page server, covering browsing, reading, searching, previewing edits, and submitting writes without unnecessary duplication. Each tool has a clear role in the workflow.
Read, browse, search, edit-preview, and submit workflows are covered, and the preview-before-submit flow is well defined. The main gaps are the lack of explicit page deletion, page history, and a dedicated new-page submission tool, though the core page lifecycle is mostly functional.