cosense

Cosense MCP Server exposes a set of tools that let you interact with Cosense pages programmatically. The available tools include get_page to retrieve a page by title, list_pages to enumerate pages within a resource set, search_pages to find pages containing a query string, and insert_lines to insert text after a specified line in a page. With the MCP server running, you can compose commands that leverage these tools to automate content retrieval, page creation or updates, and batch edits on your Cosense project. The server is designed to work over standard input/output, making it compatible with MCP clients and automation scripts that orchestrate page operations against your Cosense workspace.

Prerequisites:

• Node.js installed on your system
• Access to a Cosense project with a valid COSENSE_PROJECT_NAME and COSENSE_SID (session cookie) for authentication

Installation steps (example using Node.js server):

1. Clone or download the repository for the Cosense MCP server
2. Install dependencies:

pnpm install
# or
npm install

3. Build the server (if required by the project setup):

pnpm run build
# or
npm run build

4. Configure your MCP client to connect to the server using the Node command and the built index.js entry point:

{
  "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"
      }
    }
  }
}

5. Start the MCP server and connect your MCP client to it using the configuration above.

Note: If you prefer VS Code or Claude Desktop workflows, you can follow the environment-specific snippets in the README and adapt them to point at your local build or installed package.

Environment variables:

• COSENSE_PROJECT_NAME: your Cosense project name
• COSENSE_SID: session cookie for authentication (read/write access depending on your setup)

Tips:

• Keep COSENSE_SID secure as it allows authenticated actions.
• If you modify build outputs or paths, ensure the MCP client uses the updated index.js path.
• The server communicates over stdio; when debugging, consider using the MCP Inspector tool as described in the Debugging section of the README.
• For local development, you can run from source and point the MCP client to the local build path as shown in the development examples.