Castor Mcp

com.moosejudgePublished by moosejudge.comv0.6.2Updated Oct 24, 2026

Castor for Confluence Data Center — MCP server bridging Confluence DC with AI agents

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Castor is a local MCP server that connects an AI assistant to a Confluence Data Center instance so it can work with that wiki's content.

What you can do
Connect an AI assistant to a Confluence Data Center instance through a local MCP server. Use standard operations authenticated with a personal access token, plus optional elevated or admin operations with a separate token. The manifest does not list individual tools, so the exact actions available are not documented here.
When to use it
Worth adding when your team keeps documentation, pages or knowledge in a self-hosted Confluence Data Center instance and you want an assistant to work with that content directly. Not useful if you use Confluence Cloud or have no Confluence instance.
Requirements
A local runtime that can run the npm package castor-mcp over stdio, on a desktop machine. The base URL of the Confluence Data Center instance in CONFLUENCE_URL, and a personal access token in CONFLUENCE_USER_TOKEN. Network access to that instance.
Before you install
Requires personal access tokens: CONFLUENCE_USER_TOKEN for standard operations and an optional CONFLUENCE_ADMIN_TOKEN for elevated or admin operations. The admin token grants broader rights, so provide it only when needed. The manifest does not document which tools write, change or delete Confluence content, so check before letting an assistant modify pages.

Installation

In SourceWeft

  1. Open Castor Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.2LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.