Arca

build.arca.mcpPublished by mcp.arca.buildOfficial publisherv0.0.1Updated Oct 24, 2026

Arca is a private data vault where your AI stores your structured data, semantic memory and skills.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Arca is a remote private data vault MCP server that lets an AI assistant store and retrieve your structured data, semantic memory and skills.

What you can do
Store structured data in a private vault managed by the assistant through Arca's tools, which are not itemized in the listing. Keep semantic memory so the assistant can recall context across sessions. Hold reusable skills in the same vault. Access is authenticated per user through a bearer token or OAuth.
When to use it
Worth adding when you want an assistant to keep persistent, private memory, structured records and reusable skills in one hosted vault rather than in local files or a single chat.
Requirements
A remote MCP endpoint at mcp.arca.build over streamable HTTP. Authentication is required: an Authorization header carrying either a bearer token (API key obtained on arca.build) or an OAuth flow. No local runtime or packages are needed.
Before you install
The vault holds your private structured data, memory and skills, so review what the assistant is allowed to store and who can reach the account. The Authorization credential is a secret; keep it out of shared logs and prompts. Data is kept on a third-party hosted service, so consider its retention and access policies before storing sensitive material.

Installation

In SourceWeft

  1. Open Arca 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/build.arca.mcp%2Farca-mcp-server/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": {
    "arca": {
      "type": "http",
      "url": "https://mcp.arca.build/"
    }
  }
}

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. v0.0.1LatestSep 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.