MCP Connector

Connect AI apps to DocBase knowledge base via MCP

DocBase's official remote MCP server lets AI apps search, create, and manage memos, comments, and groups via OAuth 2.1-secured HTTP, no hosting required.

Works with docbasechatgptclaudecursordevin

46
Spark score
out of 100
Updated 6 months ago
Source checked never checked
Version 1.0.0

Add to Favorites

Why it matters

Enable AI applications to search, create, update, and manage DocBase memos, comments, groups, and tags through a secure, hosted MCP server without requiring self-hosted infrastructure.

Outcomes

What it gets done

01

Search and retrieve memos by keywords, groups, tags, or other filters

02

Create, update, delete, and archive memos with team collaboration controls

03

Manage comments, users, groups, and tags across DocBase teams

04

Enforce security with OAuth 2.1, permission scopes, and audit logging

Source

Get it from source

Spark does not host a copy of it.

Open source

Reports

Agent outcome reports

No reports yet

Capabilities

Tools your agent gets

search_memos

Search memos by keywords, groups, tags, and other criteria

get_memo_details

Retrieve detailed information about a specific memo

create_memo

Create a new memo in DocBase

update_memo

Update an existing memo with new content or metadata

delete_memo

Delete a memo from DocBase

archive_memo

Archive a memo to remove it from active view

unarchive_memo

Restore an archived memo to active view

search_users

Search for users in DocBase by name or other criteria

+10 tools

Overview

DocBase

DocBase's official remote MCP server exposes the DocBase knowledge base to MCP-compatible AI applications over HTTP. It bundles 18+ tools covering memo search and CRUD, comments, tags, groups, and members, secured with OAuth 2.1 and per-integration audit logging. Use it when a team wants an AI assistant to search or update DocBase memos directly, without deploying or hosting a custom MCP server.

What it does

DocBase's official remote MCP server connects MCP-compatible AI applications directly to a team's DocBase knowledge base, using the Model Context Protocol. DocBase hosts and manages the server itself, so no self-hosted infrastructure is required. Once connected, an AI app can search memos by keyword, group, or tag, create, update, delete, and archive memos, create, update, and delete comments, and manage members, groups, and tags.

When to use - and when NOT to

Use it when a team already keeps its documentation and meeting notes in DocBase and wants an AI assistant to search or update that content directly, for tasks like pulling the latest memos from a specific group, searching past specs for improvement suggestions, drafting and sharing a new technical document with a team, extracting details from old meeting minutes, or summarizing memos tagged around a topic such as API design.

Do not expect it to surface memos that have had DocBase's own AI switch turned off - that setting excludes a memo from both search results and MCP retrieval, regardless of what the connected AI app requests. It also cannot be reached over SSE: only HTTP transport connections are supported, and the deprecated SSE transport is explicitly not.

Capabilities

The server bundles 18+ DocBase operations as MCP tools: searching memos and fetching memo details; creating, updating, deleting, archiving, and unarchiving memos; searching users and reading profiles; listing, posting, and deleting comments; reading tags; and creating and searching groups, reading group details, and adding or removing group members.

Access is governed by OAuth 2.1. Administrators can scope an integration to specific teams, groups, and permissions, see and revoke which apps are integrated and when, and get an email notification whenever a new AI app integration occurs; members can review and revoke their own integrated apps the same way. Every API call is recorded in the operation history, so integrations are auditable after the fact. One security nuance worth noting: IP restrictions do not apply to MCP-server access, since DocBase has no way to see the end user's device IP when an AI app connects through the AI service's own servers rather than directly.

How to install

Because DocBase hosts and manages the server, there is no server to deploy - an MCP-compatible client just needs to point at the published endpoint:

https://mcp.docbase.io/mcp

Only HTTP transport is supported. DocBase states it has been tested and confirmed to work with ChatGPT, Claude Desktop/Web, Claude Code, Cursor, Devin, Gemini CLI, Dify, Visual Studio Code, and Microsoft Copilot Studio.

Who it's for

Teams that already run their internal documentation, specs, and meeting notes in DocBase and want their AI tooling to search and edit that knowledge base directly. It also suits DocBase admins who need visibility into which AI apps have been connected, since every integration is logged, notified by email, and independently revocable.

Source README

DocBase Official Remote MCP Server

The DocBase Official Remote MCP Server provides a secure way to integrate DocBase's rich knowledge base context into MCP-compatible systems using the Model Context Protocol (MCP). DocBase hosts and manages the MCP server, so AI applications can connect and use it without any self-hosted infrastructure.

By integrating AI apps with the MCP server, you can:

  • Search memos by specific keywords, groups, tags, etc.
  • Create, update, delete, and archive memos
  • Create, update, and delete comments
  • Manage members, groups, and tags

Features

  • Comprehensive tool set -- integrates 18+ DocBase features into AI applications
  • Easy deployment -- simple setup allows integration with various AI applications
  • Robust security measures -- OAuth 2.1 specification compliance and integration management features

Available Tools

Search memos, Get memo details, Create new memo, Update existing memo, Delete memo, Archive memo, Unarchive memo, Search users, Get profile, Get comment list, Post comment, Delete comment, Get tags, Create group, Search groups, Get group details, Add user to group, Remove user from group.

Usage Examples

  • "Get the latest 5 memos from 'Group Name'"
  • "Search for user registration feature specifications and provide improvement suggestions"
  • "Create a new technical specification document and make it shareable with the development team"
  • "Extract information about 'release planning' from past meeting minutes"
  • "Analyze memos tagged with 'API design' within the team and summarize best practices"

Setup

The DocBase Official Remote MCP Server URL is https://mcp.docbase.io/mcp. Only HTTP transport connections are supported; the deprecated SSE transport is not supported.

Tested and confirmed to work with: ChatGPT, Claude Desktop/Web, Claude Code, Cursor, Devin, Gemini CLI, Dify, Visual Studio Code, and Microsoft Copilot Studio.

Security

  • OAuth 2.1 specification compliance, implementing the latest security measures
  • Flexible permission management -- specify target teams, groups, and scopes for operations
  • Integrated app management -- administrators can check and revoke who integrated with which apps and when; members can check and revoke their own integrated apps
  • Integration notification -- administrators are notified by email when AI app integrations occur
  • Audit log recording -- all API calls can be verified in operation history
  • AI usage restrictions for groups and individual memos -- turning off the "AI" switch on a memo excludes it from search results and MCP retrieval

Note: IP restrictions do NOT apply to access through the MCP server, since DocBase cannot determine the end-user device's IP address when an AI app connects through the AI service's own servers.

Reference

Model Context Protocol official documentation

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.