cosense

This MCP server provides access to cosense via the MCP protocol. It exposes a dedicated server named cosense-mcp-server that runs the built index.js with Node.js and accepts configuration through environment variables. To connect clients (such as Claude Desktop) you point the MCP client at the server by using the host and port where the server is running and supplying the necessary COSENSE project details via COSENSE_PROJECT_NAME and, optionally, COSENSE_SID for private projects. The server supports the Get Page capability (as indicated by the Features list), enabling clients to retrieve cosense pages or related data as defined by the cosense integration. For debugging, you can use the MCP Inspector to inspect stdio-based MCP communication during development (the inspector is invoked via npm run inspector).

When configuring through Claude Desktop, provide the path to the built server (build/index.js) and set environment variables as shown in the examples. If COSENSE_SID is not required for your project, you can omit it, but COSENSE_PROJECT_NAME is typically required to identify the project context.

Prerequisites:

• Node.js (and npm) installed on your system
• Access to a shell/terminal

Installation steps:

1. Clone the repository git clone https://github.com/funwarioisii/cosense-mcp-server.git
2. Change into the project directory cd cosense-mcp-server
3. Install dependencies npm run install
4. Build the server npm run build

Optional for development:

• Start in watch mode for auto-rebuild during development npm run watch

To configure with Claude Desktop:

• Ensure the built server path is correct in your Claude config, e.g.: { "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" } } } }

Notes and tips:

• MCP servers communicate over stdio; debugging can be challenging without a dedicated inspector. The MCP Inspector tool (npm run inspector) provides a browser-based debugging interface.
• COSENSE_SID is optional and only needed if you're using a private Cosense project. If you don’t require a private project, you can omit COSENSE_SID.
• Ensure COSENSE_PROJECT_NAME accurately matches your Cosense project to route data correctly.
• When deploying, point the Node.js server to the built index.js (build/index.js) to ensure the latest changes are used.
• If you encounter permission or path issues, verify that the absolute path to build/index.js is correct and that the environment variables are exported to the process running the MCP server.