# Flare Developers

> Build with the same context Flare uses. MCP for agents, SDK for Nori, API when you want to be programmatic.

## Install sketch

```
FLARE_API_TOKEN=$FLARE_TOKEN npx -y flare-mcp

<script src="https://flares.in/sdk/flare.min.js"></script>
```

## 01 · MCP

Connect Claude, ChatGPT, Cursor, and Grok. Read and write the graph. Scoped. Async. Verified against acceptance criteria.

MCP story: https://flares.in/mcp

## 02 · SDK

Embed Nori. One script. The widget is the front desk; the brain is still Flare.

## 03 · API

Personal access tokens, hashed and scoped. Same graph the agents use. Rate-limited. Audited.

- REST API base: https://flares.in/api/v1
- OpenAPI specification: https://flares.in/openapi.json
- Auth: `Authorization: Bearer flr_pat_...` (personal access token) or `flr_oat_...` (MCP OAuth token)
- Errors: structured JSON — `{ error: { code, message }, request_id }`

## 04 · Your agents

Flare does not have to build every worker. Bring your own agent. Give it a memory.

---
Machine-readable site summary: https://flares.in/llms.txt · Site map: https://flares.in/sitemap.xml
