Skip to main content
Glama
deenesjakoruzh
jem-computer

Capacities MCP Server

by jem-computer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Capacities MCP Plus

Capacities用の拡張MCP（Model Context Protocol）サーバーであり、ナレッジマネジメントシステムとのシームレスな統合を提供します。

注: これはjemgold/capacities-mcpのフォークであり、機能追加と修正が行われています。

オリジナルとの違い

機能

オリジナル

Plus

オブジェクト内容の読み取り

利用不可

オブジェクトIDによるノート全文の取得

fastmcpバージョン

1.27.3

3.25.4 (MCP SDKの互換性を修正)

Windowsサポート

問題がある可能性あり

cmdラッパーでテスト済み

npmパッケージ

capacities-mcp

capacities-mcp-plus

新しいツール: capacities_read_object_content

IDを使用してCapacitiesオブジェクトの全文を取得します：

  • 直接取得のために、まず非公開のAPIエンドポイントを試行します

  • 直接アクセスできない場合は、検索API集約にフォールバックします

  • 検索精度を向上させるためにtitleパラメータを提供します

Related MCP server: ClickUp MCP Server

機能

このMCPサーバーは、現在のすべてのCapacities APIエンドポイントへのアクセスを提供します：

  • スペースの一覧表示 - 個人の全スペースを取得

  • スペース情報 - 詳細なスペース構造とコレクションを取得

  • コンテンツの検索 - 高度なフィルタリングを使用してスペース全体を検索

  • オブジェクト内容の読み取り - オブジェクトIDでノート全文を取得

  • Webリンクの保存 - メタデータ付きでURLをスペースに保存

  • デイリーノート - デイリーノートにコンテンツを追加

インストール

Claude Desktop (macOS) の場合

Claude Desktopの設定ファイル (~/Library/Application Support/Claude/claude_desktop_config.json) に追加してください：

{
  "mcpServers": {
    "capacities": {
      "command": "npx",
      "args": ["-y", "capacities-mcp-plus"],
      "env": {
        "CAPACITIES_API_KEY": "your_capacities_api_key_here"
      }
    }
  }
}

Claude Desktop (Windows) の場合

Windowsではcmdラッパーが必要です。%APPDATA%\Claude\claude_desktop_config.json に追加してください：

{
  "mcpServers": {
    "capacities": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "capacities-mcp-plus"],
      "env": {
        "CAPACITIES_API_KEY": "your_capacities_api_key_here"
      }
    }
  }
}

Capacitiesアカウント設定からCapacities APIキーを取得してください。

以上です！Claude Desktopの起動時にサーバーが自動的にダウンロードされ、実行されます。

開発

ローカルセットアップ

ローカル開発には、プロジェクトのクローンとビルドが必要です：

  1. リポジトリをクローンします：

git clone https://github.com/Im-Hal-9K/capacities-mcp.git
cd capacities-mcp

  1. 依存関係をインストールします：

npm install
# or
bun install

  1. 環境変数のサンプルファイルをコピーします：

cp .env.example .env

  1. .env にCapacities APIキーを追加します：

CAPACITIES_API_KEY=your_api_key_here

  1. サーバーをビルドします：

npm run build

サーバーの実行

インタラクティブモードで開発サーバーを起動します：

bun run dev

本番環境で使用する場合：

npm run start

サーバーのツールとスキーマを検査するには：

bun run inspect

テスト

テストスイートを実行します：

bun run test

コード品質

リンティングと型チェックを実行します：

bun run lint

コードをフォーマットします：

bun run format

APIリファレンス

Capacitiesアカウント設定からCapacities APIキーを取得してください。

詳細なAPIドキュメントについては、以下を参照してください：

利用可能なツール

capacities_list_spaces

個人の全スペースのリストを取得します。

capacities_get_space_info

構造やコレクションを含む、特定のスペースに関する詳細情報を取得します。

  • spaceId: スペースのUUID

capacities_search

オプションのフィルタリングを使用して、スペース全体からコンテンツを検索します。

  • searchTerm: 検索するテキスト

  • spaceIds: 検索対象のスペースUUIDの配列

  • mode (オプション): "fullText" または "title" 検索モード

  • filterStructureIds (オプション): 特定の構造タイプでフィルタリング

capacities_read_object_content

IDを使用してCapacitiesオブジェクトの全文を取得します。

  • objectId: 取得するオブジェクトのUUID（Capacitiesの「オブジェクト参照をコピー」から取得可能）

  • spaceId: オブジェクトを含むスペースのUUID

  • title (オプション): オブジェクトのタイトルまたはタイトルの一部 - 検索結果を向上させるために強く推奨されます

  • 仕組み:

    1. まず、直接オブジェクトを取得するために非公開のGETエンドポイントを試行します

    2. 失敗した場合は検索APIにフォールバックし、ハイライトやスニペットからコンテンツを集約します

    3. 検索結果をオブジェクトIDでフィルタリングして完全一致を探します

  • 注: 検索フォールバックを使用する場合、検索スニペットから組み立てられるため、コンテンツが不完全になる可能性があります。titleパラメータを指定すると結果が大幅に向上します。

capacities_save_weblink

オプションのメタデータ付きでWebリンクをスペースに保存します。

  • spaceId: ターゲットスペースのUUID

  • url: 保存するURL

  • titleOverwrite (オプション): リンクのカスタムタイトル

  • descriptionOverwrite (オプション): 説明テキスト

  • tags (オプション): タグの配列。タグはCapacities内のタグ名と完全に一致している必要があります。一致しない場合は作成されます。

  • mdText (オプション): ノートセクションに追加されるMarkdown形式のテキスト

capacities_save_to_daily_note

スペース内の今日のデイリーノートにMarkdownコンテンツを追加します。

  • spaceId: ターゲットスペースのUUID

  • mdText: 追加するMarkdownコンテンツ

  • origin (オプション): コンテンツの発生元ラベル（"commandPalette"のみサポート）

  • noTimestamp (オプション): trueの場合、ノートにタイムスタンプは追加されません

レート制限

Capacities APIには以下のレート制限があります：

  • /spaces: 60秒間に5リクエスト

  • /space-info: 60秒間に5リクエスト

  • /search: 60秒間に120リクエスト

  • /save-weblink: 60秒間に10リクエスト

  • /save-to-daily-note: 60秒間に5リクエスト

プロンプト例

このMCPサーバーが設定されている場合にClaudeで使用できるプロンプト例をいくつか紹介します：

はじめに

"Show me all my Capacities spaces"
"What spaces do I have in Capacities?"

ナレッジベースの探索

"Get detailed information about my main workspace in Capacities"
"What structures and collections are in my [space name] space?"

コンテンツの検索

"Search for 'project management' across all my Capacities spaces"
"Find all notes mentioning 'machine learning' in my research space"
"Search for 'meeting notes' but only check titles, not full content"

コンテンツの読み取り

"Read the content of object [object-id] from my research space"
"Get the full note content for [title] in my workspace"

情報の保存

"Save this article to my research space: https://example.com/article"
"Bookmark this GitHub repo in my coding space with tags 'javascript' and 'tools'"
"Save this link with a custom title and description to my resources space"

デイリーノート

"Add a summary of today's key insights to my daily note"
"Save these meeting notes to today's daily note in my work space"
"Add this quote to my daily note: [your quote here]"

高度な使用法

"Search for 'productivity' in my work and personal spaces, but filter to only show task-related structures"
"Save this research paper to my academic space and add it to today's daily note as well"
"Find all my notes about 'AI tools' and then save the best ones as bookmarks"

クレジット

ライセンス

MIT - 詳細は LICENSE ファイルを参照してください。

Available Tools

5 tools
capacities_get_space_infoA
Read-only

Get detailed information about a specific Capacities space including structures and collections

ParametersJSON Schema
NameRequiredDescriptionDefault
spaceIdYesThe UUID of the space to get information for

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation that may return varying data. The description adds value by specifying what information is included ('structures and collections'), which provides useful context beyond the annotations. However, it doesn't mention rate limits, authentication needs, or response format details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose and includes relevant scope details ('including structures and collections'). There's no wasted language, and every element serves to clarify the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with one parameter and good annotations, the description is reasonably complete. It specifies what information is returned, which compensates for the lack of an output schema. However, it could be more complete by mentioning the response format or any limitations, though annotations cover the safety profile adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the single parameter 'spaceId' fully documented as 'The UUID of the space to get information for'. The description doesn't add any additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating with extra details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get detailed information') and resource ('a specific Capacities space'), including scope ('including structures and collections'). It distinguishes from 'capacities_list_spaces' by focusing on a single space rather than listing multiple spaces, but doesn't explicitly differentiate from other siblings like 'capacities_search'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through 'a specific Capacities space' and the required spaceId parameter, suggesting this tool is for retrieving details about a known space. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'capacities_search' or mention any prerequisites beyond having a space ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

capacities_list_spacesB
Read-only

Get a list of all personal spaces in Capacities

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation that may return incomplete data. The description adds minimal behavioral context beyond this—it specifies 'all personal spaces' but doesn't mention pagination, rate limits, or what 'personal spaces' entails. With annotations covering safety, a 3 is appropriate as the description adds some value but not rich behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan. Every part of the sentence earns its place by conveying essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, read-only operation), the description is adequate but has gaps. Annotations cover safety, but there's no output schema, so the description doesn't explain return values (e.g., format of the list). For a list operation, more context on output structure would be helpful, but the description meets minimum viability.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description correctly doesn't mention any parameters, which is appropriate. Baseline for 0 parameters is 4, as no parameter semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get a list') and resource ('all personal spaces in Capacities'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'capacities_get_space_info' (which presumably gets details for a specific space), but the scope is clear. The description avoids tautology by not just repeating the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'capacities_search' (which might search within spaces) or 'capacities_get_space_info' (which gets details for a specific space), nor does it specify any prerequisites or contexts for use. The agent must infer usage from the description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

capacities_save_to_daily_noteB

Add markdown text to today's daily note in a Capacities space

ParametersJSON Schema
NameRequiredDescriptionDefault
mdTextYesThe markdown text to add to today's daily note
noTimestampNoIf true, no time stamp will be added to the note
originNoOptional origin label for the content (only 'commandPalette' is supported)
spaceIdYesThe UUID of the space to save to the daily note

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false (implying a write operation) and openWorldHint=true (suggesting flexible use), which the description aligns with by describing an 'Add' action. However, it doesn't add significant behavioral context beyond annotations, such as whether the text is appended or overwritten, or any rate limits or permissions needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action and resource without unnecessary details. It's appropriately sized for the tool's complexity, with zero waste or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (4 parameters, no output schema) and rich annotations, the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral nuances, or output expectations, leaving gaps that could hinder an AI agent's effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the input schema fully documents all parameters, including mdText, noTimestamp, origin, and spaceId. The description mentions 'markdown text' and 'today's daily note', which loosely maps to mdText and implies a date context, but adds minimal semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Add markdown text') and target resource ('today's daily note in a Capacities space'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like capacities_save_weblink, which might also involve saving content but to different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as capacities_save_weblink for saving links or capacities_search for finding notes. It lacks context on prerequisites (e.g., needing a valid spaceId) or exclusions, leaving usage unclear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updatesv1.0.0
    • First observedcapacities_get_space_info
    • First observedcapacities_list_spaces
    • First observedcapacities_save_to_daily_note
    • First observedcapacities_save_weblink
    • First observedcapacities_search
Deploy Server
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_space_info retrieves metadata about a specific space, list_spaces enumerates all spaces, save_to_daily_note adds content to a daily note, save_weblink stores web links, and search performs content searches. There is no overlap or ambiguity in their functions, making it easy for an agent to select the right tool.

Naming Consistency5/5

All tool names follow a consistent 'capacities_verb_noun' pattern, using snake_case throughout. This predictability aids in understanding and usage, with no deviations in naming conventions across the set.

Tool Count5/5

With 5 tools, the server is well-scoped for its purpose of interacting with Capacities spaces. Each tool serves a specific and necessary function, such as listing spaces, retrieving info, saving content, and searching, without being overly sparse or bloated.

Completeness4/5

The tool set covers key operations for managing Capacities spaces, including listing, retrieving info, saving notes and links, and searching. A minor gap exists in lacking update or delete operations for saved content, but agents can work around this for most workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers