# Other apps

> Connect any app that supports remote MCP servers, with sign-in or an API key, and test the server yourself.

Any app that supports remote MCP servers can use Geniffy. Give it the server URL; if it supports OAuth, it
opens the Geniffy sign-in, and otherwise it can send an API key.

```text
https://api.geniffy.com/mcp
```

## Apps that sign in

Add the URL as a remote, HTTP (Streamable HTTP) server. The app finds Geniffy's sign-in by itself: it gets a
`401` from the server, reads where to sign in, registers itself, and opens Geniffy in your browser. Sign in
and press **Allow**. Most apps take an entry like this:

```json
{
  "mcpServers": {
    "geniffy": {
      "url": "https://api.geniffy.com/mcp"
    }
  }
}
```

## Apps that cannot sign in

Send a Geniffy API key as a header. Make one under **API keys** in the Geniffy app:

```text
Authorization: Bearer gnf_live_...
```

A key reaches what it reaches in the API. With a key, every tool also takes an optional `space`, to work in
the memory of one of your app's users.

## Test it yourself

The MCP Inspector connects, signs in and calls tools, which makes it the quickest way to see what an app
will see:

```bash
npx @modelcontextprotocol/inspector
```

Choose **Streamable HTTP**, enter the server URL, and connect.

## What the server speaks

- **Transport:** Streamable HTTP. Every request is a `POST` answered with JSON. There is no server-to-client
  stream, so `GET` answers `405`, and no session to keep.
- **Protocol versions:** `2025-11-25`, `2025-06-18`, `2025-03-26` and `2024-11-05`. An app that asks for
  another is answered in the newest.
- **Tools only:** eight tools, each with an input schema, an output schema and annotations that say which
  ones change your memory. See [Tools](https://docs.geniffy.com/mcp/tools).
- **Browsers:** the server and its sign-in accept calls from any origin, with a bearer token and never a
  cookie, so an app that runs in a web page can connect too.

Source: https://docs.geniffy.com/mcp/other-clients