Skip to main content
Tekma’s MCP server exposes capture context to compatible clients over Streamable HTTP.

​
Connect with your account

Add that URL as a remote HTTP MCP server in your client. Start its authentication flow and approve access in Tekma using the account that can view the relevant workspace. For Claude Code, add the server from your terminal:
Use the client’s MCP authentication controls to sign in if prompted. Client interfaces vary by version; the required server URL and access checks are the same.

​
Investigate a capture

Start with the capture details, then ask for the relevant console messages, network requests, actions, or frames. A useful prompt includes the capture reference and the behavior to investigate:
Inspect this capture, identify the failed request around the checkout error, and explain which evidence supports the diagnosis.
The server includes tools such as getDetails, getConsoleLogs, getNetworkRequests, getDiagnosis, and getFrames. The client’s tool list is the current reference for available arguments. For a read-only investigation, clients that support custom headers can send the authorized share URL in mcp-capture-share. The server accepts the full URL or its share-token tail. The share’s permissions still apply. A Without DevTools link does not become a diagnostic share just because an agent opens it through MCP. Expiry and revocation also apply. Keep the header value out of public configuration files and source control. It grants access to the shared content.

​
Scopes and limits

  • captures:read reads permitted capture content.
  • captures:record authorizes recording uploads.
  • comments:write authorizes comment creation.
  • captures:write authorizes supported capture changes.
Workspace membership and feature policy are enforced separately from scopes. If a write tool requests additional authorization, approve only the operation your workflow needs. To create a recording from an agent, use the CLI and recorder skill.