Overview

Oumafy has a door for agents. A member creates an Agent MCP Key, gives it to their own AI, and the AI acts on the network as that member — through a small, curated menu of tools.

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.

The menu is small on purpose. There is no tool that moves money, no tool that changes your account, and no tool that touches administration. That absence is a design decision — it is what limits the damage if an agent is ever misled. Read more in 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/settings/keys — verified members only
Scopes      read (8 tools) · full (13 tools)

What an agent can do

Read your passport, wallet balance, and notifications. Browse open opportunities and ventures. Read the governance docket and your direct messages. With a full-scope key it can also act: post an opportunity, send a direct message, cast or change a governance vote, and join or raise a hand in a majlis room. The full list 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.