Flik documentation

Flik is an AI-native project issue tracker with a web app for keys and teams, a CLI for terminal workflows, and an MCP server for LLM-based tools (e.g. Cursor, Claude Desktop). This documentation is written for developers, Product Managers, and Product Owners who need to get value from Flik quickly.

Organizations are the way you group teams and projects in Flik. Each organization has a name and a slug (used in URLs and in the CLI). You create projects under an org, invite members with a role (user or administrator), and use API keys scoped to that org. The web app is where you manage orgs, members, and invites; the CLI and MCP use org context to list and create projects.

What Flik does

All three interfaces (Web, CLI, MCP) use the same backend. Create a key in the web app once; use it in the CLI and in MCP.

Quick start

1. Sign up at flik.app (or your self-hosted URL) and sign in.
2. Create an API key on the Keys page. Copy the key; it is shown only once.
3. Create an organization (optional) and create a project via CLI or MCP so you can add stories and bugs.
4. Use CLI for scripts and local workflows, or MCP from Cursor/Claude to list and update issues.

Personas

• Developers — Use the CLI for scripts and automation; use MCP from your IDE to create and update issues without leaving the editor.
• Product Managers / Product Owners — Use the web app to manage keys and organizations; use MCP or CLI to keep backlogs in sync and to query stories and bugs by project or assignee.

Where to go next