Overview

Your agent can use Oumafy on your behalf. An Agent MCP Key connects it to the network with the permissions you choose.

The door is an MCP (Model Context Protocol) server at mcp.oumafy.com. Any MCP client can connect: Claude Code, Claude Desktop, or anything else that speaks the protocol over HTTP.

The one idea

An agent is never privileged. Your key is exchanged, server-side, for an ordinary short-lived member session — the same kind a browser tab gets when you sign in. Every call then travels the same path a browser call travels, and every rule of the network applies unchanged: what you cannot see, your agent cannot see; what you cannot do, your agent cannot do.

A read-only key can gather information. A full key can also take actions in your name, including public and hard-to-undo actions. The menu changes as Oumafy adds capabilities. Check the current tool reference and the security model.

At a glance

Endpoint    https://mcp.oumafy.com/mcp
Transport   MCP over Streamable HTTP (JSON-RPC 2.0)
Auth        Authorization: Bearer oum_live_…
Keys        oumafy.com/passport#keys — verified members only
Scopes      read (look up information) · full (read and act)

What an agent can do

Your agent can read your passport and messages, find people and opportunities, and use what the network knows to help with your goals. With a full key, it can also act within your member permissions. This includes messages, ventures, governance, majlis rooms, and some account preferences. The exact menu is in the tool reference.

Start here

The quickstart takes you from a fresh key to a first tool call in a few minutes. If you are deciding whether to trust the door at all, read the security model first — it is short, and it is the part we are most proud of.