Your assistant can use these tools, not just read about them.

Three facts, and any assistant can use it

Mint a key in the app — Settings → API keys — and every client needs the same three things. There is nothing vendor-specific in the handshake.

Where those three go depends on what you use:

Claude

claude mcp add --transport http invora https://your-install/mcp \
  --header "Authorization: Bearer apk_xxxx"

The desktop and web apps take the same URL and header when you add it as a custom connector.

ChatGPT and the OpenAI API

{
  "type": "mcp",
  "server_label": "invora",
  "server_url": "https://your-install/mcp",
  "authorization": "apk_xxxx",
  "require_approval": "never"
}

That is one entry in the Responses API's tools array. In ChatGPT itself, the same URL and key go in as a connector.

A client that keeps servers in a config file

Own Your AI, editors like VS Code and Cursor, and most desktop clients read a list like this:

{
  "mcpServers": [
    { "id": "invora", "name": "Invora", "url": "https://your-install/mcp",
      "token": "apk_xxxx", "enabled": true }
  ]
}

A local model, n8n, or your own code

n8n's MCP Client node takes the URL and the same Authorization: Bearer header. A model running on your own machine reaches it through any MCP client — nothing leaves your network at all in that setup. And if you would rather write it yourself, it is plain JSON-RPC 2.0 over one POST:

curl -X POST https://your-install/mcp \
  -H "Authorization: Bearer apk_xxxx" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Any client that speaks MCP's streamable-HTTP transport works, including ones that do not exist yet — the endpoint implements the protocol, not an integration with a particular vendor. The exact tool list for each product is in the API.md inside its download.

A key that can only read

When you mint the key you choose what it may do. Pick Read only and the endpoint stops advertising the tools that change anything — an assistant asks its questions and is refused, by name, if it tries to write. Pick read and write and it behaves as it always has. Either way the key acts as one user and inherits that user's role, and you can revoke it from the same page at any moment.

Or run the assistant yourself too

The recipe above works with any MCP client, hosted ones included. If you would rather not send your business data to somebody else's model, Own Your AI is our own client: it runs on your machine, connects to these same endpoints, and can talk to a model you host locally. Same three facts — id, url, token — in its own config.

Own Your AI →

Every tool in the catalog speaks it

274 tools across 48 products, listed below exactly as each product declares them to tools/list. A ✎ marks a tool that can change something; the rest only read. Hover a name for what it does. Mint a read-only key and the write tools are not advertised to the assistant at all.

Since the 3.0 release, all 48 of them — every product here except Own Your AI, which is the client you connect with rather than a server you connect to. Each product page links its own tool list.