Skip to main content
Glama
Cosense MCP Server

Cosense MCP Server

by funwarioisii

cosense-mcp-server MCP 서버

CoSense 용 MCP 서버

특징

  • 페이지 가져오기

Related MCP server: cc-session-search

개발

종속성 설치:

지엑스피1

서버를 빌드하세요:

npm run build

자동 재빌드를 사용한 개발의 경우:

npm run watch

설치

git clone https://github.com/funwarioisii/cosense-mcp-server.git
cd cosense-mcp-server
npm run install
npm run build

Claude Desktop과 함께 사용하려면 서버 구성을 추가하세요.

MacOS의 경우: ~/Library/Application\ Support/Claude/claude_desktop_config.json Windows의 경우: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "cosense-mcp-server": {
      "command": "node",
      "args": ["/path/to/cosense-mcp-server/build/index.js"],
      "env": {
        "COSENSE_PROJECT_NAME": "your_project_name",
        "COSENSE_SID": "your_sid"
      }
    }
  }
}

COSENSE_SID 는 선택 사항입니다. 이 서버를 비공개 프로젝트에 사용하려면 COSENSE_SID 설정해야 합니다.

디버깅

MCP 서버는 stdio를 통해 통신하므로 디버깅이 어려울 수 있습니다. 패키지 스크립트로 제공되는 MCP Inspector를 사용하는 것이 좋습니다.

npm run inspector

검사기는 브라우저에서 디버깅 도구에 액세스할 수 있는 URL을 제공합니다.

Available Tools

2 tools
get_pageC
    Get a page from my-project project on cosen.se

    In cosense, a page is a cosense-style document with a title and a description.
    Bracket Notation makes links between pages.
    Example: [Page Title]
    -> "/my-project/Page Title"

    A page may have links to other pages.
    Links are rendered at the bottom of the page.
    

Inputs: pageTitle (required).

list_pagesB

List known cosense pages from my-project project on cosen.se

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: 'get_page' retrieves a specific page with its content and links, while 'list_pages' enumerates all known pages. There is no overlap or ambiguity between them, as one is for detailed retrieval and the other for listing.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with snake_case: 'get_page' and 'list_pages'. The naming is predictable and readable, with no deviations or mixed conventions, making it easy to understand their functions at a glance.

    Tool Count2/5

    With only 2 tools, the server feels too thin for its apparent domain of managing pages in a project. It lacks essential operations like creating, updating, or deleting pages, which are typical for such a domain, making it under-scoped and limiting for agents.

    Completeness2/5

    The tool surface is severely incomplete for page management. While it provides read operations (get and list), it misses critical CRUD functions such as create, update, and delete, as well as other potential operations like searching or managing links. This will likely cause agent failures in handling full page lifecycles.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers