Capacities

io.capacitiesPublished by capacities.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Connect an AI assistant to a Capacities space (objects, daily notes, search).

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Connects an AI assistant to a Capacities space so it can work with objects, daily notes, and search.

What you can do
This remote MCP server links an assistant to a Capacities space. According to the registry description, it covers objects, daily notes, and search, letting the assistant reach the notes and structured content stored in that space. No individual tools are listed in the manifest.
When to use it
Worth adding when you keep notes and structured objects in Capacities and want an assistant to search or work with that content directly instead of copying it elsewhere.
Requirements
A remote endpoint at api.capacities.io reached over streamable HTTP, plus a Capacities account and OAuth sign-in, which the manifest marks as required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Capacities space, so the assistant can reach the notes and objects stored there; review what the connection is allowed to do before authorizing it.

Installation

In SourceWeft

  1. Open Capacities in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.capacities%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "capacities": {
      "type": "http",
      "url": "https://api.capacities.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.