> ## 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.

# Set up Tekma for your coding agent

> Set up Tekma with one prompt, or manually install the CLI, skills and MCP connection.

Copy the setup prompt from [Tekma's agent page](https://tekma.dev/#agents) 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:

```text theme={null}
Set up Tekma for me. Read and follow https://tekma.dev/agent-setup/prompt.md to install the CLI and both agent skills, connect my coding agents to MCP, and verify the setup. Guide me through sign-in and any agent reload.
```

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:

```bash theme={null}
npx --yes @tekma/cli setup
```

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

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    npx --yes @tekma/cli setup --agent claude
    ```
  </Tab>

  <Tab title="Codex">
    ```bash theme={null}
    npx --yes @tekma/cli setup --agent codex
    ```
  </Tab>

  <Tab title="Cursor">
    ```bash theme={null}
    npx --yes @tekma/cli setup --agent cursor
    ```
  </Tab>

  <Tab title="Copilot">
    ```bash theme={null}
    npx --yes @tekma/cli setup --agent copilot
    ```
  </Tab>
</Tabs>

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

```bash theme={null}
npx --yes @tekma/cli setup --skip-login --json
npx --yes @tekma/cli auth status --json
npx --yes @tekma/cli doctor
```

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:

```bash theme={null}
npx --yes @tekma/cli skills install --directory /PATH/TO/SKILLS
```

See [MCP configuration](/developers/mcp), [skills](/developers/skill), [CLI installation](/developers/installation) and [authentication](/developers/authentication) for individual setup and recovery.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.