Skip to main content
Copy the setup prompt from Tekma’s agent page and paste it into Claude Code, Codex, Cursor or Copilot. Your agent follows the maintained guide, installs the CLI and both skills, connects MCP, and verifies setup. You can also copy the prompt here:
Complete browser sign-in when prompted. Reload your agent if needed, then approve its native MCP connection on first use. The CLI and each agent have separate authorization; passwords and tokens belong in their native stores.

​
Manual setup

Requires Node.js 22.17 or newer. Run one command to configure detected agent profiles:
This installs tekma-recorder and tekma-reader, configures MCP, saves the CLI endpoint and opens browser sign-in. A global install is optional.

​
Choose one agent

Use --project for project-local skills and MCP configuration, or --skip-login to configure files without signing in. For self-hosted Tekma, pass --server https://YOUR_MCP_ORIGIN/mcp.

​
Check the result

Setup should report ready, list your intended agent and show no conflicts. Online auth status should report authenticated: true with server verification. A successful configuration-only run does not establish authentication. Doctor checks the browser and ffmpeg prerequisites before recording.

​
Existing configuration and other agents

Matching files and valid CLI sign-in are reused. Customized, invalid or linked files are preserved and reported as conflicts. Inspect those paths and retain unrelated settings before retrying. For an unsupported agent, install skills into its documented directory and add the HTTP MCP server through its native connection settings:
See MCP configuration, skills, CLI installation and authentication for individual setup and recovery.