# {{ package_name }}

{{ display_name }} MCP (Model Context Protocol) server, generated by [mcpify](https://github.com/guercheLE/mcpify).

Exposes exactly 3 tools — `search`, `get`, `call` — backed by an embedded semantic database (`mcp_store.db`), so an LLM never needs the full API surface in context.

## Install

```bash
npm install
npm run build
```

## Setup

```bash
npm run setup
```

Interactively collects the API URL and the credentials your chosen auth method needs, then lets you persist them as a `.env` file, a `config.json` file, or a ready-to-run CLI invocation.

## Usage

### Terminal Client (default)

```bash
{{ project_name }} search "create an issue"
{{ project_name }} get <operationId>
{{ project_name }} call <operationId> --some-arg value
```

### Harness Server

```bash
{{ project_name }} start                              # stdio transport (default)
{{ project_name }} http --host 127.0.0.1 --port 3000  # HTTP transport
```

## Testing

```bash
npm test
```

## Coverage

```bash
npm run test:coverage       # writes coverage/index.html + coverage/coverage-final.json
```

## Profiling

```bash
bash scripts/profile.sh   # writes profile/bottleneck-report.md, profile/cpu-profile.txt, profile/heap.heapprofile
```

`profile/bottleneck-report.md` combines CPU and memory hot-path summaries in one small text file — paste it into an LLM (or hand it to another tool) to find and fix bottlenecks. For the interactive heap view, load one of the files in `profile/heap/` in Chrome DevTools' Memory tab.

---

Generated by mcpify — do not hand-edit generated files; re-run mcpify against an updated OpenAPI spec instead.
