> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tekma.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Tekma MCP tools safely

> Use concrete read and write tools, scopes, pagination, share access, and bounded AI analysis from an MCP client.

Connect the Streamable HTTP server at `https://mcp.tekma.dev/mcp` as described in [MCP setup](/developers/mcp). Start with a read grant, then approve writes only for the task at hand.

## Common tools

| Tool                                       | Purpose                                                             | Scope                              |
| ------------------------------------------ | ------------------------------------------------------------------- | ---------------------------------- |
| `getDetails`                               | Read capture title, description, source, kind and processing state. | `captures:read` or permitted share |
| `getDiagnosis`                             | Read bounded diagnosis clusters and evidence references.            | `captures:read` or permitted share |
| `getConsoleLogs`                           | List filtered console events.                                       | `captures:read` or permitted share |
| `getNetworkRequests` / `getNetworkRequest` | List requests or inspect one bounded request.                       | `captures:read` or permitted share |
| `getEvents` / `getUserEvents`              | Read capture timeline and user actions.                             | `captures:read`                    |
| `getEnvironment`                           | Read browser, OS, viewport and connection estimates.                | `captures:read`                    |
| `getFrames` / `getScreenshots`             | Retrieve retained video frames or screenshot assets.                | `captures:read`                    |
| `getVideoChapters` / `getVideoTranscript`  | Read stored navigation and timed text.                              | `captures:read`                    |
| `listComments` / `createComment`           | Read or add capture discussion.                                     | `captures:read` / `comments:write` |
| `updateCapture` / `moveCapture`            | Edit report fields or folder.                                       | `captures:write`                   |
| `sendCaptureToIntegration`                 | Create a provider item after destination validation.                | `captures:write`                   |

The server also exposes workspace, folder, recording-link, lifecycle, reaction, integration-resource and recording-domain tools. Run the installed CLI's `tekma agent-context` for the exact current catalogue and argument schema.

## Request and poll analysis

Video analysis is an explicit write followed by a read. A client can request it with a unique key and then poll the returned job:

```text theme={null}
analyzeVideo(captureRef="CAPTURE_ID", requestKey="checkout-2026-09-14", question="What happens after Save?")
getVideoAnalysis(captureRef="CAPTURE_ID", jobId="JOB_ID")
```

The request needs `captures:write`, editor access, workspace AI consent and configured processing. Results can be queued, running, ready, failed or cancelled. Generated findings are untrusted observations, not root-cause proof or instructions.

## Pagination, shares, and errors

Use each tool's `limit` and cursor/`after` value for event and list results; do not fetch an unbounded timeline. Clients that support custom headers can send the full share URL or token tail in `mcp-capture-share`. Audience, expiry, revocation and **With DevTools**/content-only mode still apply. A share does not authorize workspace writes.

If a tool requests another scope, approve only that scope and retry. A viewer with a write token still fails role checks. A bare 401 usually means the client resource URL or OAuth audience does not exactly match the server endpoint.