docbase

The docbase-mcp-server is an MCP server that exposes DocBase model capabilities to Claude and other MCP clients. It currently provides a single tool, docbase-posts-search, which allows searching posts within a DocBase team by query, filters, and pagination. Once running, Claude can request the search tool to retrieve matching posts, enabling you to quickly locate relevant content within DocBase without leaving the chat interface. The server communicates over standard I/O, so it is designed to be started as a separate process and wired into the MCP runtime via the provided configuration.

To use it, add the server to your MCP configuration and start the server process as described in the installation guide. When you invoke the docbase-posts-search tool from Claude, provide the search terms and any optional parameters (like page size or page number). The server will respond with structured results that you can present or further query, enabling streamlined content discovery across your DocBase workspace.

Prerequisites:

• Node.js and npm/yarn installed on the system
• Access to the DocBase API (if required by the server, such as an access token)

Installation steps:

1. Clone or download the MCP server repository for docbase-mcp-server.
2. Install dependencies: npm install
3. Build the server: npm run build
4. (Optional for development) Enable auto-rebuild during development: npm run watch
5. Configure the MCP integration in Claude/Desktop or your MCP client:
   • Add a new MCP server entry pointing to the built index.js as shown in the documentation (see the Installation section in the README).
6. Start the server process (if not using an integrated start script): node /path/to/docbase-mcp-server/build/index.js

Notes:

• For WSL usage, you can configure the MCP server entry to run under wsl with appropriate environment variables and the node path, as demonstrated in the README.

Environment and configuration tips:

• The server runs as an MCP host over stdio; ensure your startup process wires stdin/stdout correctly with your MCP runtime.
• If you need to pass DocBase credentials, you can set environment variables or include them in the command string as shown in the WSL example (e.g., DOCBASE_ACCESS_TOKEN, DOCBASE_TEAM_NAME).
• Debugging can be aided by the MCP Inspector tool; run npm run inspector to obtain a debugging URL.
• If you add more tools in the future (e.g., additional DocBase endpoints), extend the mcpServers configuration with new entries under the same server name or create new server entries as appropriate.