Referna Meeting Recaps

by referna-aiio.github.referna-ai/meeting-recapsv1.0.0

How the score works

Read your personalized Referna meeting recaps with an AI assistant.

  • Remote endpoint

Uptime

Checked  · every day

100%from 8 days of checks

Up without downtime on 7 of 7 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 349 ms, slowest 5% 417 ms for the handshake and the tool list, over 30 days.

400 ms200 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

2 tools at the last answer.

Every day
DayResultChecksMedian
7 Nov (today)No verdict yet0–
6 NovNo downtime1of 1387 ms
5 NovNo downtime1of 1358 ms
4 NovNo downtime1of 1349 ms
3 NovNo downtime1of 1369 ms
2 NovNo downtime1of 1340 ms
1 NovNo downtime1of 1358 ms
31 OctNo downtime2350 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):

{
  "mcpServers": {
    "meeting-recaps": {
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}

Replace YOUR_AUTHORIZATION with your own value.

For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server Referna Meeting Recaps (`io.github.referna-ai/meeting-recaps`)

Its page: https://plug.directory/servers/io.github.referna-ai/meeting-recaps

It runs on the publisher's servers; the client connects to its URL.

Ask the person for `YOUR_AUTHORIZATION` and put it in place of the placeholder; never invent a value.

Use the section for the person's client.

## Claude Desktop

This server needs a header that the connector form cannot set; use Claude Code, Cursor or VS Code for it.

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport http meeting-recaps https://referna.com/mcp/member-recaps --header 'Authorization: YOUR_AUTHORIZATION'
```

## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "meeting-recaps": {
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "meeting-recaps": {
      "type": "http",
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "meeting-recaps": {
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## Cline

Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):

```json
{
  "mcpServers": {
    "meeting-recaps": {
      "type": "streamableHttp",
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## Continue

This server needs a header, and Continue's documentation shows no way to send one to a remote server; use another client for it.

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "meeting-recaps":
    type: streamable_http
    name: "meeting-recaps"
    enabled: true
    uri: "https://referna.com/mcp/member-recaps"
    headers: { "Authorization": "YOUR_AUTHORIZATION" }
    env_keys: []
    envs: {}
    timeout: 300
```

## Gemini CLI

Merge into ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "meeting-recaps": {
      "httpUrl": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## Codex

Add to ~/.codex/config.toml:

```toml
[mcp_servers.meeting-recaps]
url = "https://referna.com/mcp/member-recaps"
http_headers = { "Authorization" = "YOUR_AUTHORIZATION" }
```

## mcp-client-cli, TUUI, BoltAI

This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "meeting-recaps": {
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "meeting-recaps": {
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## AnythingLLM

Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:

```json
{
  "mcpServers": {
    "meeting-recaps": {
      "type": "streamable",
      "url": "https://referna.com/mcp/member-recaps",
      "headers": { "Authorization": "YOUR_AUTHORIZATION" }
    }
  }
}
```

## Augment Code

This server needs a header, and Augment Code's documentation shows no way to send one to a remote server; use another client for it.

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem