MCP or CLI is not working

Start outside the AI client so authentication and project failures are visible directly:

teml whoami
teml projects list
teml doctor

For API-key use, confirm TEML_API_KEY is available to the process that launches the CLI or MCP client—not only to your interactive shell.

The MCP client cannot connect

Confirm the remote URL and bearer key match Connect an MCP client. Restart the client after changing its configuration. A key needs mcp:read; write tools also need mcp:write and their domain scopes.

If the connection succeeds but no tools appear, inspect the client’s MCP logs for an authentication response and verify it supports remote HTTP MCP. Do not paste the key into chat.

A CLI command returns the wrong project or no rows

teml projects use my-app
teml persons search test-user

Check environment and time filters next. Piped CLI output is JSON; interactive output is formatted, so a parser should consume the piped form rather than scraping terminal tables.

A write is missing or refused

Destructive CLI commands require --yes. MCP clients may also require an interactive confirmation. If a tool is absent, the server may have hidden it because the key lacks mcp:write or the relevant domain permission. Regenerate a purpose-specific key instead of broadening a shared key.

Use teml docs --markdown to confirm the installed CLI’s exact command and flag surface. Upgrade or pin the CLI if an automation was written for a different early-access version.

• Use the Teml CLI
• Permissions and safe actions