Works with
Any MCP-capable agent, including your own
Nemosyne has no favourite agent. It speaks the Model Context Protocol, one endpoint per organisation, and anything that speaks MCP can connect — a vendor's assistant, an internal copilot, or something you wrote yourself this afternoon.
How the connection works.
- Create your organisation. It gets its own MCP endpoint.
- Point your agent at that endpoint. OAuth 2.1 runs in front, and each person signs in as themselves.
- Call the tools. Their descriptions are generated from the concepts your firm has adopted, so an agent is told what your firm tracks rather than having to guess.
What the endpoint offers.
- Protocol
- MCP, at one endpoint per organisation.
- Sign-in
- OAuth 2.1, per person, brokered at the gateway. Machine credentials exist for machines and are not how a person connects.
- Tools
- Recall, search, entity context and attributed writes.
What the gateway will not do.
It will not answer as somebody else: there is no impersonation path and no shared service account, and a call returns only what the caller is allowed to see.
What we enforce, and the limits we publish →Questions this raises.
- Is there a REST API as well?
- MCP is the supported front door for agents. It is what the gateway is for, and it is the path every shipped client uses.
- Can we run it inside our own perimeter?
- Yes. Private cloud and self-host both exist, and on either the model calls run under your own keys.
Connect the agent you already use.
Free for three people and about a hundred documents. No card, no expiry.
Start free →