cue-ai 0.3.0 → 0.4.1

package/resources/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcp-server/references/remote-http-scaffold.md

@@ -1,211 +0,0 @@
-# Remote Streamable-HTTP MCP Server — Scaffold
-
-Minimal working servers in both recommended frameworks. Start here, then add tools.
-
----
-
-## TypeScript SDK (`@modelcontextprotocol/sdk`)
-
-```bash
-npm init -y
-npm install @modelcontextprotocol/sdk zod express
-npm install -D typescript @types/express @types/node tsx
-```
-
-**`src/server.ts`**
-
-```typescript
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-import { StreamableHTTPServerTransport } from "@modelcontextprotocol/sdk/server/streamableHttp.js";
-import express from "express";
-import { z } from "zod";
-
-const server = new McpServer(
-  { name: "my-service", version: "0.1.0" },
-  { instructions: "Prefer search_items before calling get_item directly — IDs aren't guessable." },
-);
-
-// Pattern A: one tool per action
-server.registerTool(
-  "search_items",
-  {
-    description: "Search items by keyword. Returns up to `limit` matches ranked by relevance.",
-    inputSchema: {
-      query: z.string().describe("Search keywords"),
-      limit: z.number().int().min(1).max(50).default(10),
-    },
-    annotations: { readOnlyHint: true },
-  },
-  async ({ query, limit }, extra) => {
-    // extra.signal is an AbortSignal — check it in long loops for cancellation
-    const results = await upstreamApi.search(query, limit);
-    return {
-      content: [{ type: "text", text: JSON.stringify(results, null, 2) }],
-    };
-  },
-);
-
-server.registerTool(
-  "get_item",
-  {
-    description: "Fetch a single item by its ID.",
-    inputSchema: { id: z.string() },
-    annotations: { readOnlyHint: true },
-  },
-  async ({ id }) => {
-    const item = await upstreamApi.get(id);
-    return { content: [{ type: "text", text: JSON.stringify(item) }] };
-  },
-);
-
-// Streamable HTTP transport (stateless mode — simplest)
-const app = express();
-app.use(express.json());
-
-app.post("/mcp", async (req, res) => {
-  const transport = new StreamableHTTPServerTransport({
-    sessionIdGenerator: undefined, // stateless
-  });
-  res.on("close", () => transport.close());
-  await server.connect(transport);
-  await transport.handleRequest(req, res, req.body);
-});
-
-app.listen(process.env.PORT ?? 3000);
-```
-
-**Stateless vs stateful:** The snippet above creates a fresh transport per request (stateless). Fine for most API-wrapping servers. If tools need to share state across calls in a session (rare), use a session-keyed transport map — see the SDK's `examples/server/simpleStreamableHttp.ts`.
-
----
-
-## FastMCP 3.x (Python)
-
-```bash
-pip install fastmcp
-```
-
-**`server.py`**
-
-```python
-from fastmcp import FastMCP
-
-mcp = FastMCP(
-    name="my-service",
-    instructions="Prefer search_items before calling get_item directly — IDs aren't guessable.",
-)
-
-@mcp.tool(annotations={"readOnlyHint": True})
-def search_items(query: str, limit: int = 10) -> list[dict]:
-    """Search items by keyword. Returns up to `limit` matches ranked by relevance."""
-    return upstream_api.search(query, limit)
-
-@mcp.tool(annotations={"readOnlyHint": True})
-def get_item(id: str) -> dict:
-    """Fetch a single item by its ID."""
-    return upstream_api.get(id)
-
-if __name__ == "__main__":
-    mcp.run(transport="http", host="0.0.0.0", port=3000)
-```
-
-FastMCP derives the JSON schema from type hints and the docstring becomes the tool description. Keep docstrings terse and action-oriented — they land in Claude's context window verbatim.
-
----
-
-## Search + execute pattern (large API surface)
-
-When wrapping 50+ endpoints, don't register them all. Two tools:
-
-```typescript
-const CATALOG = loadActionCatalog(); // { id, description, paramSchema }[]
-
-server.registerTool(
-  "search_actions",
-  {
-    description: "Find available actions matching an intent. Call this first to discover what's possible. Returns action IDs, descriptions, and parameter schemas.",
-    inputSchema: { intent: z.string().describe("What you want to do, in plain English") },
-    annotations: { readOnlyHint: true },
-  },
-  async ({ intent }) => {
-    const matches = rankActions(CATALOG, intent).slice(0, 10);
-    return { content: [{ type: "text", text: JSON.stringify(matches, null, 2) }] };
-  },
-);
-
-server.registerTool(
-  "execute_action",
-  {
-    description: "Execute an action by ID. Get the ID and params schema from search_actions first.",
-    inputSchema: {
-      action_id: z.string(),
-      params: z.record(z.unknown()),
-    },
-  },
-  async ({ action_id, params }) => {
-    const action = CATALOG.find(a => a.id === action_id);
-    if (!action) throw new Error(`Unknown action: ${action_id}`);
-    validate(params, action.paramSchema);
-    const result = await dispatch(action, params);
-    return { content: [{ type: "text", text: JSON.stringify(result) }] };
-  },
-);
-```
-
-`rankActions` can be simple keyword matching to start. Upgrade to embeddings if precision matters.
-
----
-
-## Test it
-
-The MCP Inspector connects to any transport and lets you poke tools interactively.
-
-```bash
-# Interactive — opens a UI on localhost:6274
-npx @modelcontextprotocol/inspector
-# → select "Streamable HTTP", paste http://localhost:3000/mcp, Connect
-```
-
-For scripted checks (CI, smoke tests):
-
-```bash
-npx @modelcontextprotocol/inspector --cli http://localhost:3000/mcp \
-  --transport http --method tools/list
-
-npx @modelcontextprotocol/inspector --cli http://localhost:3000/mcp \
-  --transport http --method tools/call --tool-name search_items --tool-arg query=test
-```
-
----
-
-## Connect users
-
-Once deployed, users add the URL directly — no install step.
-
-| Surface | How |
-|---|---|
-| **Claude Code** | `claude mcp add --transport http <name> <url>` (add `--scope user` for global, `--header "Authorization: Bearer ..."` for auth) |
-| **Claude Desktop / Claude.ai** | Settings → Connectors → Add custom connector. **Not** `claude_desktop_config.json` — remote servers configured there are ignored. |
-| **Connector directory** | Anthropic maintains a submission guide for listing in the public connector directory. |
-
----
-
-## Deploy
-
-**Fastest path:** Cloudflare Workers — two commands from zero to a live `https://` URL on the free tier. Uses a Workers-native scaffold (not Express). → `deploy-cloudflare-workers.md`
-
-**This Express scaffold** runs on any Node host — Render, Railway, Fly.io, a VPS. Containerize it (`node:20-slim`, copy, `npm ci`, `node dist/server.js`) and ship. FastMCP is the same story with a Python base image.
-
----
-
-## Deployment checklist
-
-- [ ] `POST /mcp` responds to `initialize` with server capabilities
-- [ ] `tools/list` returns your tools with complete schemas
-- [ ] Errors return structured MCP errors, not HTTP 500s with HTML bodies
-- [ ] CORS headers set if browser clients will connect
-- [ ] `Origin` header validated on `/mcp` (spec MUST — DNS rebinding prevention)
-- [ ] `MCP-Protocol-Version` header honored (return 400 for unsupported versions)
-- [ ] `instructions` field set if tool-use needs hints
-- [ ] Health check endpoint separate from `/mcp` (hosts poll it)
-- [ ] Secrets from env vars, never hardcoded
-- [ ] If OAuth: CIMD or DCR endpoint implemented — see `auth.md`

package/resources/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcp-server/references/resources-and-prompts.md

@@ -1,122 +0,0 @@
-# Resources & Prompts — the other two primitives
-
-MCP defines three server-side primitives. Tools are model-controlled (Claude decides when to call them). The other two are different:
-
-- **Resources** are application-controlled — the host decides what to pull into context
-- **Prompts** are user-controlled — surfaced as slash commands or menu items
-
-Most servers only need tools. Reach for these when the shape of your integration doesn't fit "Claude calls a function."
-
----
-
-## Resources
-
-A resource is data identified by a URI. Unlike a tool, it's not *called* — it's *read*. The host browses available resources and decides which to load into context.
-
-**When a resource beats a tool:**
-- Large reference data (docs, schemas, configs) that Claude should be able to browse
-- Content that changes independently of conversation (log files, live data)
-- Anything where "Claude decides to fetch" is the wrong mental model
-
-**When a tool is better:**
-- The operation has side effects
-- The result depends on parameters Claude chooses
-- You want Claude (not the host UI) to decide when to pull it in
-
-### Static resources
-
-```typescript
-// TypeScript SDK
-server.registerResource(
-  "config",
-  "config://app/settings",
-  { name: "App Settings", description: "Current configuration", mimeType: "application/json" },
-  async (uri) => ({
-    contents: [{ uri: uri.href, mimeType: "application/json", text: JSON.stringify(config) }],
-  }),
-);
-```
-
-```python
-# fastmcp
-@mcp.resource("config://app/settings")
-def get_settings() -> str:
-    """Current application configuration."""
-    return json.dumps(config)
-```
-
-### Dynamic resources (URI templates)
-
-RFC 6570 templates let one registration serve many URIs:
-
-```typescript
-import { ResourceTemplate } from "@modelcontextprotocol/sdk/server/mcp.js";
-
-server.registerResource(
-  "file",
-  new ResourceTemplate("file:///{path}", { list: undefined }),
-  { name: "File", description: "Read a file from the workspace" },
-  async (uri, { path }) => ({
-    contents: [{ uri: uri.href, text: await fs.readFile(path, "utf8") }],
-  }),
-);
-```
-
-```python
-@mcp.resource("file:///{path}")
-def read_file(path: str) -> str:
-    return Path(path).read_text()
-```
-
-### Subscriptions
-
-Resources can notify the client when they change. Declare `subscribe: true` in capabilities, then emit `notifications/resources/updated`. The host re-reads. Useful for log tails, live dashboards, watched files.
-
----
-
-## Prompts
-
-A prompt is a parameterized message template. The host surfaces it as a slash command or menu item. The user picks it, fills in arguments, and the resulting messages land in the conversation.
-
-**When to use:** canned workflows users run repeatedly — `/summarize-thread`, `/draft-reply`, `/explain-error`. Near-zero code, high UX leverage.
-
-```typescript
-server.registerPrompt(
-  "summarize",
-  {
-    title: "Summarize document",
-    description: "Generate a concise summary of the given text",
-    argsSchema: { text: z.string(), max_words: z.string().optional() },
-  },
-  ({ text, max_words }) => ({
-    messages: [{
-      role: "user",
-      content: { type: "text", text: `Summarize in ${max_words ?? "100"} words:\n\n${text}` },
-    }],
-  }),
-);
-```
-
-```python
-@mcp.prompt
-def summarize(text: str, max_words: str = "100") -> str:
-    """Generate a concise summary of the given text."""
-    return f"Summarize in {max_words} words:\n\n{text}"
-```
-
-**Constraints:**
-- Arguments are **string-only** (no numbers, booleans, objects) — convert inside the handler
-- Returns a `messages[]` array — can include embedded resources/images, not just text
-- No side effects — the handler just builds a message, it doesn't *do* anything
-
----
-
-## Quick decision table
-
-| You want to... | Use |
-|---|---|
-| Let Claude fetch something on demand, with parameters | **Tool** |
-| Expose browsable context (files, docs, schemas) | **Resource** |
-| Expose a dynamic family of things (`db://{table}`) | **Resource template** |
-| Give users a one-click workflow | **Prompt** |
-| Ask the user something mid-tool | **Elicitation** (see `elicitation.md`) |

package/resources/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcp-server/references/server-capabilities.md

@@ -1,164 +0,0 @@
-# Server capabilities — the rest of the spec
-
-Features beyond the three core primitives. Most are optional, a few are near-free wins.
-
----
-
-## `instructions` — system prompt injection
-
-One line of config, lands directly in Claude's system prompt. Use it for tool-use hints that don't fit in individual tool descriptions.
-
-```typescript
-const server = new McpServer(
-  { name: "my-server", version: "1.0.0" },
-  { instructions: "Always call search_items before get_item — IDs aren't guessable." },
-);
-```
-
-```python
-mcp = FastMCP("my-server", instructions="Always call search_items before get_item — IDs aren't guessable.")
-```
-
-This is the highest-leverage one-liner in the spec. If Claude keeps misusing your tools, put the fix here.
-
----
-
-## Sampling — delegate LLM calls to the host
-
-If your tool logic needs LLM inference (summarize, classify, generate), don't ship your own model client. Ask the host to do it.
-
-```typescript
-// Inside a tool handler
-const result = await extra.sendRequest({
-  method: "sampling/createMessage",
-  params: {
-    messages: [{ role: "user", content: { type: "text", text: `Summarize: ${doc}` } }],
-    maxTokens: 500,
-  },
-}, CreateMessageResultSchema);
-```
-
-```python
-# fastmcp
-response = await ctx.sample("Summarize this document", context=doc)
-```
-
-**Requires client support** — check `clientCapabilities.sampling` first. Model preference hints are substring-matched (`"claude-3-5"` matches any Claude 3.5 variant).
-
----
-
-## Roots — query workspace boundaries
-
-Instead of hardcoding a root directory, ask the host which directories the user approved.
-
-```typescript
-const caps = server.getClientCapabilities();
-if (caps?.roots) {
-  const { roots } = await server.server.listRoots();
-  // roots: [{ uri: "file:///home/user/project", name: "My Project" }]
-}
-```
-
-```python
-roots = await ctx.list_roots()
-```
-
-Particularly relevant for MCPB local servers — see `build-mcpb/references/local-security.md`.
-
----
-
-## Logging — structured, level-aware
-
-Better than stderr for remote servers. Client can filter by level.
-
-```typescript
-// In a tool handler
-await extra.sendNotification({
-  method: "notifications/message",
-  params: { level: "info", logger: "my-tool", data: { msg: "Processing", count: 42 } },
-});
-```
-
-```python
-await ctx.info("Processing", count=42)   # also: ctx.debug, ctx.warning, ctx.error
-```
-
-Levels follow syslog: `debug`, `info`, `notice`, `warning`, `error`, `critical`, `alert`, `emergency`. Client sets minimum via `logging/setLevel`.
-
----
-
-## Progress — for long-running tools
-
-Client sends a `progressToken` in request `_meta`. Server emits progress notifications against it.
-
-```typescript
-async (args, extra) => {
-  const token = extra._meta?.progressToken;
-  for (let i = 0; i < 100; i++) {
-    if (token !== undefined) {
-      await extra.sendNotification({
-        method: "notifications/progress",
-        params: { progressToken: token, progress: i, total: 100, message: `Step ${i}` },
-      });
-    }
-    await doStep(i);
-  }
-  return { content: [{ type: "text", text: "Done" }] };
-}
-```
-
-```python
-async def long_task(ctx: Context) -> str:
-    for i in range(100):
-        await ctx.report_progress(progress=i, total=100, message=f"Step {i}")
-        await do_step(i)
-    return "Done"
-```
-
----
-
-## Cancellation — honor the abort signal
-
-Long tools should check the SDK-provided `AbortSignal`:
-
-```typescript
-async (args, extra) => {
-  for (const item of items) {
-    if (extra.signal.aborted) throw new Error("Cancelled");
-    await process(item);
-  }
-}
-```
-
-fastmcp handles this via asyncio cancellation — no explicit check needed if your handler is properly async.
-
----
-
-## Completion — autocomplete for prompt args
-
-If you've registered prompts or resource templates with arguments, you can offer autocomplete:
-
-```typescript
-server.registerPrompt("query", {
-  argsSchema: {
-    table: completable(z.string(), async (partial) => tables.filter(t => t.startsWith(partial))),
-  },
-}, ...);
-```
-
-Low priority unless your prompts have many valid values.
-
----
-
-## Which capabilities need client support?
-
-| Feature | Server declares | Client must support | Fallback if not |
-|---|---|---|---|
-| `instructions` | implicit | — | — (always works) |
-| Logging | `logging: {}` | — | stderr |
-| Progress | — | sends `progressToken` | silently skip |
-| Sampling | — | `sampling: {}` | bring your own LLM |
-| Elicitation | — | `elicitation: {}` | return text, ask Claude to relay |
-| Roots | — | `roots: {}` | config env var |
-
-Check client caps via `server.getClientCapabilities()` (TS) or `ctx.session.client_params.capabilities` (fastmcp) before using the bottom three.

package/resources/claude-plugins-official/plugins/mcp-server-dev/skills/build-mcp-server/references/tool-design.md

@@ -1,189 +0,0 @@
-# Tool Design — Writing Tools Claude Uses Correctly
-
-Tool schemas and descriptions are prompt engineering. They land directly in Claude's context and determine whether Claude picks the right tool with the right arguments. Most MCP integration bugs trace back to vague descriptions or loose schemas.
-
-## Anthropic Directory hard requirements
-
-If this server will be submitted to the Anthropic Directory, the following are pass/fail review criteria (full list: https://claude.com/docs/connectors/building/review-criteria):
-
-- Every tool **must** include `readOnlyHint`, `destructiveHint`, and `title` annotations — these determine auto-permissions in Claude.
-- Tool names **must** be ≤64 characters.
-- Read and write operations **must** be in separate tools. A single tool accepting both GET and POST/PUT/PATCH/DELETE is rejected — documenting safe vs unsafe within one tool's description does not satisfy this.
-- Tool descriptions **must not** instruct Claude how to behave (e.g. "always do X", "you must call Y first", overriding system instructions, promoting products) — treated as prompt injection at review.
-- Tools that accept freeform API endpoints/params **must** reference the target API's documentation in their description.
-
----
-
-## Descriptions
-
-**The description is the contract.** It's the only thing Claude reads before deciding whether to call the tool. Write it like a one-line manpage entry plus disambiguating hints.
-
-### Good
-
-```
-search_issues — Search issues by keyword across title and body. Returns up
-to `limit` results ranked by recency. Does NOT search comments or PRs —
-use search_comments / search_prs for those.
-```
-
-- Says what it does
-- Says what it returns
-- Says what it *doesn't* do (prevents wrong-tool calls)
-
-### Bad
-
-```
-search_issues — Searches for issues.
-```
-
-Claude will call this for anything vaguely search-shaped, including things it can't do.
-
-### Disambiguate siblings
-
-When two tools are similar, each description should say when to use the *other* one:
-
-```
-get_user      — Fetch a user by ID. If you only have an email, use find_user_by_email.
-find_user_by_email — Look up a user by email address. Returns null if not found.
-```
-
----
-
-## Parameter schemas
-
-**Tight schemas prevent bad calls.** Every constraint you express in the schema is one fewer thing that can go wrong at runtime.
-
-| Instead of | Use |
-|---|---|
-| `z.string()` for an ID | `z.string().regex(/^usr_[a-z0-9]{12}$/)` |
-| `z.number()` for a limit | `z.number().int().min(1).max(100).default(20)` |
-| `z.string()` for a choice | `z.enum(["open", "closed", "all"])` |
-| optional with no hint | `.optional().describe("Defaults to the caller's workspace")` |
-
-**Describe every parameter.** The `.describe()` text shows up in the schema Claude sees. Omitting it is leaving money on the table.
-
-```typescript
-{
-  query: z.string().describe("Keywords to search for. Supports quoted phrases."),
-  status: z.enum(["open", "closed", "all"]).default("open")
-    .describe("Filter by status. Use 'all' to include closed items."),
-  limit: z.number().int().min(1).max(50).default(10)
-    .describe("Max results. Hard cap at 50."),
-}
-```
-
----
-
-## Return shapes
-
-Claude reads whatever you put in `content[].text`. Make it parseable.
-
-**Do:**
-- Return JSON for structured data (`JSON.stringify(result, null, 2)`)
-- Return short confirmations for mutations (`"Created issue #123"`)
-- Include IDs Claude will need for follow-up calls
-- Truncate huge payloads and say so (`"Showing 10 of 847 results. Refine the query to narrow down."`)
-
-**Don't:**
-- Return raw HTML
-- Return megabytes of unfiltered API response
-- Return bare success with no identifier (`"ok"` after a create — Claude can't reference what it made)
-
----
-
-## How many tools?
-
-| Tool count | Guidance |
-|---|---|
-| 1–15 | One tool per action. Sweet spot. |
-| 15–30 | Still workable. Audit for near-duplicates that could merge. |
-| 30+ | Switch to search + execute. Optionally promote the top 3–5 to dedicated tools. |
-
-The ceiling isn't a hard protocol limit — it's context-window economics. Every tool schema is tokens Claude spends *every turn*. Thirty tools with rich schemas can eat 3–5k tokens before the conversation even starts.
-
----
-
-## Errors
-
-Return MCP tool errors, not exceptions that crash the transport. Include enough detail for Claude to recover or retry differently.
-
-```typescript
-if (!item) {
-  return {
-    isError: true,
-    content: [{
-      type: "text",
-      text: `Item ${id} not found. Use search_items to find valid IDs.`,
-    }],
-  };
-}
-```
-
-The hint ("use search_items…") turns a dead end into a next step.
-
----
-
-## Tool annotations
-
-Hints the host uses for UX — red confirm button for destructive, auto-approve for readonly. All default to unset (host assumes worst case).
-
-| Annotation | Meaning | Host behavior |
-|---|---|---|
-| `readOnlyHint: true` | No side effects | May auto-approve |
-| `destructiveHint: true` | Deletes/overwrites | Confirmation dialog |
-| `idempotentHint: true` | Safe to retry | May retry on transient error |
-| `openWorldHint: true` | Talks to external world (web, APIs) | May show network indicator |
-
-```typescript
-server.registerTool("delete_file", {
-  description: "Delete a file",
-  inputSchema: { path: z.string() },
-  annotations: { destructiveHint: true, idempotentHint: false },
-}, handler);
-```
-
-```python
-@mcp.tool(annotations={"destructiveHint": True, "idempotentHint": False})
-def delete_file(path: str) -> str:
-    ...
-```
-
-Pair with the read/write split advice in `build-mcpb/references/local-security.md` — mark every read tool `readOnlyHint: true`.
-
----
-
-## Structured output
-
-`JSON.stringify(result)` in a text block works, but the spec has first-class typed output: `outputSchema` + `structuredContent`. Clients can validate.
-
-```typescript
-server.registerTool("get_weather", {
-  description: "Get current weather",
-  inputSchema: { city: z.string() },
-  outputSchema: { temp: z.number(), conditions: z.string() },
-}, async ({ city }) => {
-  const data = await fetchWeather(city);
-  return {
-    content: [{ type: "text", text: JSON.stringify(data) }],  // backward compat
-    structuredContent: data,                                    // typed output
-  };
-});
-```
-
-Always include the text fallback — not all hosts read `structuredContent` yet.
-
----
-
-## Content types beyond text
-
-Tools can return more than strings:
-
-| Type | Shape | Use for |
-|---|---|---|
-| `text` | `{ type: "text", text: string }` | Default |
-| `image` | `{ type: "image", data: base64, mimeType }` | Screenshots, charts, diagrams |
-| `audio` | `{ type: "audio", data: base64, mimeType }` | TTS output, recordings |
-| `resource_link` | `{ type: "resource_link", uri, name?, description? }` | Pointer — client fetches later |
-| `resource` (embedded) | `{ type: "resource", resource: { uri, text\|blob, mimeType } }` | Inline the full content |
-
-**`resource_link` vs embedded:** link for large payloads or when the client might not need it (let them decide). Embed when it's small and always needed.