Skip to main content
Glama
README.md
# sechscamp

Unofficial community stdio [MCP](https://modelcontextprotocol.io/) that answers questions about **vibecamp 6** from bundled public [vibe.camp](https://vibe.camp/) pages.

**This is not an official vibecamp project.** It is not run by vibecamp, not affiliated with the vibecamp team, and not official software. **sechscamp** is only an affectionate unofficial nickname for VC6 — not branding.

Host LLMs call tools; this process only retrieves sourced public-page facts. It does not call an LLM.

- **Event:** vibecamp 6 (VC6), June 17-20, 2027, Camp Ramblewood (Darlington, MD)
- **Sources:** public vibe.camp pages shipped in `knowledge/`
- **Not included:** Discord scraping, attendee PII, or authenticated my.vibe.camp data
- **Ticket prices:** this helper does not invent 2027 dollar amounts (official FAQ: check back soon)

## Run

Requires Node.js 18+.

```bash
git clone https://github.com/minntelligence/sechscamp.git
cd sechscamp
node src/index.mjs
```

Or without cloning:

```bash
npx -y github:minntelligence/sechscamp
```

The process speaks JSON-RPC 2.0 MCP on stdin/stdout (newline-delimited JSON, plus `Content-Length` framing). Logs go to stderr.

```bash
npm test
```

## MCP client config

### Claude Desktop

Add to `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "sechscamp": {
      "command": "npx",
      "args": ["-y", "github:minntelligence/sechscamp"]
    }
  }
}
```

Local checkout:

```json
{
  "mcpServers": {
    "sechscamp": {
      "command": "node",
      "args": ["/absolute/path/to/sechscamp/src/index.mjs"]
    }
  }
}
```

### Cursor

Same `mcpServers.sechscamp` block in Cursor MCP settings / `mcp.json`.

### Generic stdio

```bash
node src/index.mjs
```

Tools:

| Tool | What it does |
| --- | --- |
| `search_vc6` | Keyword search → ranked sourced snippets |
| `get_topic` | Full topic markdown / facts by id or name |
| `list_topics` | Catalog with one-line summaries |
| `ask_vc6` | Natural-language question → sourced briefing (says so when unknown) |

Unknown answers point to Discord `https://discord.gg/V6JtaMn7WC`, `team@vibe.camp`, and `support@vibe.camp` as appropriate.

Markdown files under `knowledge/` are also exposed as MCP resources (`sechscamp://knowledge/...`) when present.

## Disclaimer

Unofficial community helper. **Not run by vibecamp. Not affiliated. Not official software.** Knowledge files are extracts of **public** vibe.camp pages only. For canonical details, read [vibe.camp](https://vibe.camp/) and the [guidelines](https://vibe.camp/guidelines/). Tickets: [my.vibe.camp](https://my.vibe.camp).

## License

MIT

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation4/5

The tools are mostly distinct: list_topics and get_topic are clearly separate, while search_vc6 and ask_vc6 both retrieve information but are differentiated by keyword search vs. natural-language briefing. Some overlap exists but descriptions make the boundaries clear.

Naming Consistency4/5

All tool names follow a verb_noun pattern with lowercase and underscores (search_vc6, get_topic, list_topics, ask_vc6). The pattern is consistent, though the object varies between 'vc6' and 'topic/topics', causing slight inconsistency.

Tool Count5/5

Four tools is a well-scoped set for a focused VC6 knowledge retrieval server. Each tool has a clear purpose and none feel redundant or excessive.

Completeness5/5

The tool set covers the full retrieval workflow: listing topics, fetching a specific topic, searching, and asking natural-language questions. No obvious missing capability for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues