Connect your stack
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Loading
Viktor is an AI employee that connects to Linear natively and helps you plan, assign, and track project tasks, running 86 Linear actions for you like Fetch, Search, and Research. Ask in plain English in Slack or Microsoft Teams; Viktor does the work in Linear and reports back. Setup takes about two minutes.
Free to start · No credit card · SOC 2 Type 1 · Works in Slack & Microsoft Teams
Messages you'd actually send. Paste one into Slack or Microsoft Teams, swap in your specifics, and Viktor takes it from there.
“Create tasks in Linear from the action items in this thread.”
— you, in Slack or Teams
“Summarize what changed in Linear this week and post it here every Friday.”
— you, in Slack or Teams
“Find the tasks in Linear that are overdue and draft a status update.”
— you, in Slack or Teams
“Keep Linear in sync with our roadmap and flag anything at risk.”
— you, in Slack or Teams
Ask in plain English in Slack or Microsoft Teams. Viktor picks the right Linear actions, runs the work, and reports back. No workflows to build.
Update an existing milestone in a Linear project.
List all milestones in a Linear project.
Query data and relationships from the Linear API with natural language.
Retrieve an attachment's content by ID.
Create a new project update in Linear.
Update an existing Linear initiative.
List initiative updates in the user's Linear workspace.
Retrieve a Linear project update by ID.
Create a new initiative update in Linear.
Create a new initiative in Linear.
Update an existing Linear initiative update.
Create a new milestone in a Linear project.
Update an existing Linear project update.
Delete (archive) an existing Linear initiative update.
Create a new Linear issue.
Update an existing Linear issue.
Create a new project in Linear.
Update an existing Linear project.
List project updates in the user's Linear workspace.
Archive a customer need in Linear.
Delete a customer in Linear.
Create a comment on a specific Linear issue.
Create or update a milestone in a Linear project. If id is provided, updates the existing milestone; otherwise creates a new one. When creating, name is required.
Delete a Linear comment. Inline description comments (those with non-null quotedText) anchor a mark in the editor, so their root cannot be deleted — delete the replies individually or resolve the thread instead.
Create or update a Linear customer. If id is provided, updates the existing customer; otherwise creates a new one. When creating, name is required.
Delete (archive) a project or initiative status update.
List Linear diff pull requests visible to the authenticated user.
Retrieve the profile of the currently authenticated user.
Send a natural-language query to Linear and get a response. Use this tool for complex queries, analytics, multi-step actions, and any request that spans multiple entities or requires reasoning — for example "what's blocking my projects?", "summarize this week's updates for my teams", or "create an issue and assign it to the frontend team". This tool can search, create, and update issues, projects, initiatives, documents, comments, labels, customers, and more. Prefer this tool over making multiple individual API calls when the task involves cross-referencing data, generating summaries, or performing actions that require context. This tool also has access to data that is not exposed through other tools. If you are not able to find the right tool send a query to the research tool to search further. Supports multi-turn conversations by passing the returned conversationId.
Full-text search across Linear issues, projects, initiatives, and documents, ranked by relevance. Use this for keyword or natural-language queries (e.g. "memory leak in sync engine"). Supports "quoted phrases" for exact match, -term to exclude, and +term to require. For structured filtering by assignee, status, team, label, etc., use the listissues or listprojects tools instead.
Fetch a Linear issue, project, initiative, or document by entity-prefixed ID. Use to get full details for results returned by the search tool. Also works with any known identifier.
Update an existing Linear document.
Create a new document in Linear.
Exact lookup for a Linear diff. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs.
List or get project/initiative status updates. Pass id to get a specific update, or filter to list.
Create or update a Linear issue. If id is provided, updates the existing issue; otherwise creates a new one. When creating, title and team are required. Note: use assignee (not assigneeId) to set the assignee — it accepts a user ID, name, email, or "me".
Prepare a direct Linear file upload for an existing issue.
Link an already-uploaded Linear assetUrl to an existing issue as an attachment.
Retrieve detailed information about an issue status in Linear by name or ID.
List available issue statuses in a Linear team.
Retrieve a Linear document by ID or slug.
Delete an attachment by ID.
List teams in the user's Linear workspace.
Extract and fetch images from markdown content. Use this to view screenshots, diagrams, or other images embedded in Linear issues, comments, or documents. Pass the markdown content (e.g., issue description) and receive the images as viewable data.
Retrieve details of a specific Linear team.
Retrieve details of a specific milestone by ID or name.
Retrieve cycles for a specific Linear team.
List available project labels in the Linear workspace.
Retrieve details of a specific project in Linear.
Create a new Linear issue label.
List available issue labels in a Linear workspace or team.
Retrieve details of a specific Linear user.
Retrieve users in the Linear workspace.
Search Linear's documentation to learn about features and usage.
List customers in the user's Linear workspace.
Retrieve detailed information about a specific initiative in Linear.
Create or update a Linear project. If id is provided, updates the existing project; otherwise creates a new one. When creating, name and at least one team (via addTeams or setTeams) are required.
Create or update a comment on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. If id is provided, updates the existing comment; otherwise creates a new one. To start a new thread, pass body and exactly one of issueId, projectId, initiativeId, documentId, milestoneId, or statusUpdateId — comments on issues/projects/initiatives become top-level discussion threads; comments on documents/milestones become description comments. A status update holds a single thread, so a comment on an update that already has one is added to it as a reply. To reply to an existing thread, pass parentId and body; the reply inherits the parent's thread type, so no entity reference is needed. Parent reference fields are ignored when id or parentId is provided (statusUpdateType is rejected instead).
List comments on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. Provide exactly one of issueId, projectId, initiativeId, documentId, milestoneId, or statusUpdateId. For issues, projects, and initiatives this returns both top-level discussion threads and inline description comments. Inline (anchored) comments carry a non-null quotedText set to the snippet of description text they reference.
Retrieve details of a release by ID or slug.
Retrieve release notes by ID or slug, including markdown content.
List Linear Agent skills available to the authenticated user.
Retrieve a Linear Agent skill by ID, including its full markdown instructions.
Create or update a customer need (request) in Linear. If id is provided, updates the existing need; otherwise creates a new one. When creating, body is required.
Create or update a project/initiative status update. Omit id to create, provide id to update.
List initiatives in the user's Linear workspace.
List documents in the user's Linear workspace.
List projects in the user's Linear workspace.
List release pipelines in the workspace.
List releases in the workspace, with optional filtering by pipeline, stage, version, and text.
Create or update a release. If id is provided, updates the existing release; otherwise creates a new one. When creating, name and pipeline are required. Release status is modeled as the release pipeline stage.
List release notes in the workspace, optionally filtered by pipeline or covered release.
Create or update release notes. If id is provided, updates the existing release notes; otherwise creates a new one. When creating, pipeline and either releases or a release range are required.
Create or update a Linear initiative. If id is provided, updates the existing initiative; otherwise creates a new one. When creating, name is required.
Merge a Linear diff or add it to the repository's merge queue.
Resolve or reopen a top-level comment thread on a Linear diff.
Delete a comment from a Linear diff.
Approve a Linear diff, request changes, or submit a review comment.
Create, reply to, or edit a comment on a Linear diff. Provide urlOrId when creating a comment or reply; provide commentId to edit an existing comment.
Deprecated fallback for tiny files only. Accepts base64 file content, verifies SHA-256 checksum, and uploads it through the MCP worker.
Retrieve detailed information about an issue by ID, including attachments, git branch name, and active Triage Intelligence suggestions when the issue is in triage.
List issues in the user's Linear workspace, including active Triage Intelligence suggestions for issues in triage. For my issues, use "me" as the assignee. Use "null" for no assignee.
List available initiative labels in the Linear workspace.
Create a new Linear initiative label.
Create or update a Linear document. If id is provided, updates the existing document; otherwise creates a new one. When creating, title is required and exactly one parent (project, issue, initiative, cycle, or team) must be specified. On update, passing a parent reparents the document. To change parts of the content without resending all of it, pass patch instead of content.
Exact lookup for diff threads. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs.
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Message Viktor in Slack like you'd message a teammate. "Create tasks in Linear from the action items in this thread." "Summarize what changed in Linear this week and post it here every Friday." Plain English, any tool.
Viktor opens Linear, runs the work, and posts back what changed. Sensitive actions wait for your approval. Everything is logged. You stop doing the work and start reviewing it.
A Linear AI agent is an AI that connects to your Linear account and completes work in it - it doesn't just answer questions about Linear, it takes the actions. Viktor is that agent: an AI employee that works in Linear on your behalf and delivers the finished result in Slack or Microsoft Teams.
Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Linear actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs.
Create and manage issues, projects, and workflows
Native integration - Viktor handles authorization itself, never sees your password, and you can revoke access at any time.
Review-first approvals: sensitive Linear actions wait for your sign-off before they run.
Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models.
SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress.
Yes. Linear is one of the 3,200+ tools Viktor connects to, as one of Viktor's native, deepest integrations. Once connected, anyone on your team can put Viktor to work in Linear from Slack or Microsoft Teams - no workflow builder, no code.
Ask for outcomes that span tools — Viktor pulls from Linear, cross-references the rest of your stack, and delivers one finished result.
Viktor connects to 3,200+ tools and works across them in a single run.
