Privatka

org.privatkaPublished by privatka.orgOfficial publisherv0.1.0Updated Nov 19, 2026

Encrypted team workspace: tasks, notes, tables, projects and time tracking. Read and write.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Privatka is a remote, OAuth-protected MCP server that gives an assistant read and write access to an encrypted team workspace of tasks, notes, tables…

What you can do
  • Work with tasks, notes, tables, projects and time tracking in an encrypted team workspace
  • Read existing workspace content and create or update it, since the server is described as read and write
  • No individual tools are documented, so the exact operations available are not specified
When to use it
Worth adding when a team keeps its tasks, notes, tables, projects and time tracking in Privatka and wants an assistant to read or update that workspace directly.
Requirements
A remote MCP endpoint at mcp.privatka.org reached over streamable HTTP. OAuth authentication is required, so a Privatka account with access to the relevant workspace is needed. No environment variables or headers are declared.
Before you install
The server is described as read and write, so an assistant may create or change tasks, notes, tables, projects and time entries in the workspace. Access is granted through OAuth to an encrypted workspace; review which workspace and permissions the authorization covers before connecting.

Installation

In SourceWeft

  1. Open Privatka 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/org.privatka%2Fprivatka/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": {
    "privatka": {
      "type": "http",
      "url": "https://mcp.privatka.org/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. v0.1.0LatestNov 19, 2026

Score

83% 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
  • 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.