Harny Context

ai.harnyPublished by harny.aiOfficial publisherv0.1.3Updated Nov 7, 2026

The backbone of your agent harness: memory, connected accounts and actions, behind one API key.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Harny Context is a remote MCP server that gives an assistant long-term memory, connected accounts and actions behind one API key.

What you can do
  • Set up long-term memory for an app without an account, creating the app and its key
  • Assemble context and inspect action history for a connected end user
  • Create calendar events, send email, open tickets, post to Slack and create Notion pages
  • Undo a previously performed action
  • Bootstrap, OAuth configuration and diagnostic helpers for the integration
When to use it
Use it when you want an assistant to keep durable memory across sessions and to act in connected accounts such as calendar, email, ticketing, Slack or Notion, rather than adding separate integrations for each.
Requirements
A remote endpoint at api.harny.ai over streamable HTTP; no local runtime or package. An Authorization header is optional: without a key, the provision_app tool creates an app and its key with no account. A runtime token scoped to one end user unlocks the action tools.
Before you install
The app key returned by provision_app is shown once and is meant for the owner's secret store; treat it as a credential. With a runtime token the assistant can send email, post messages, create tickets and pages, and change calendars, so review write actions and use undo_action where available. Actions are limited by the token's scopes.

Installation

In SourceWeft

  1. Open Harny Context in the dashboard and add it to a workspace.
  2. 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/ai.harny%2Fcontext/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.

{
  "mcpServers": {
    "harny-context": {
      "type": "http",
      "url": "https://api.harny.ai/v1/mcp/mcp"
    }
  }
}

Tools

1

provision_app

Provision App

Set up long-term memory for an app with no account: makes a new app and its key, as `POST /v1/auth/provision` does. The answer carries the app key once, and the assistant is told to put it in the owner's secret store and nowhere else. Needs no key.

Parametersapp_namerequiredcustomersobjectivemodel_presetcontact_emailassistant_name

Version history

1
  1. v0.1.3LatestNov 7, 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 listedRequired15 pts
  • 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.