Harny AI MCP Integration for AI Agents

What Harny is and what this key reaches. Harny is a private long-term memory for each person who uses an app: remember what a user tells you, recall it later, store user preferences. Returns the platform, every tool this key may call with its full schema, and the trust signals. The first call an assistant should make. Needs a key.

A ready-to-use code snippet for one Harny capability, so the code you write calls it the right way. Needs a key.

Where the app's Harny connection stands and what to do about it: the state of each part, and how fresh each connected source is. Read-only. Needs a key.

Adds a person (an end user of the app, whose long-term memory the app will keep) or returns the one that exists, as `POST /v1/users` does. The answer carries the person's key once. Needs the app's key (fsa_ prefix).

A fresh one-time link the owner opens to take ownership of this app. Use it if the link you relayed earlier expired or was lost. The link is not an API key. Needs the app's key (fsa_ prefix).

The setup bundle a coding assistant uses to stand up this app's agent in the business's own deploy: app facts, key variable names and handling rules (never key values), sources to connect, the acting policy as the business set it, the model preset, deploy recipes and the starter config, plus the rendered prompt and an installable skill file. shape is common:<path id> or developer. Read-only as far as the app's settings go: it does not change the acting policy, sources or keys. Needs the app's key (fsa_ prefix).