---
title: "Works with the tools your team already uses."
description: "Two-way Linear and Jira sync on Pro, Slack on every plan, an MCP server for AI agents and a REST API with API keys for everything else."
image: "https://feedovate.com/og/features/integrations.png"
---

# Works with the tools your team already uses.

Requests stay in step with your tracker, feedback flows in from Slack, your agents work the board over MCP, and the REST API connects the rest.

## Why it works

- Linear and Jira, both ways: Create or link an issue from a request. When your team moves the issue, the request follows, and changes flow back.
- Feedback from Slack: Turn a Slack message into a request with the customer attached, and the thread hears back when its status changes.
- Agents over MCP: Claude Code, Cursor, Codex and any MCP client can search, merge, plan and close the loop for you.

## The details

### Status mapping

Map your tracker's workflow to request statuses once, and every move after that is automatic.

### Jira from inside Jira

A Feedovate panel on each Jira issue shows the request, its customers and lets you manage it. [Feedovate for Jira on the Atlassian Marketplace](https://marketplace.atlassian.com/apps/809571407/feedovate-for-jira)

### REST API

Create requests and asks, publish changelog entries and, on Pro, sync your customers from your own tools, with API keys and an OpenAPI spec.

### Slack on every plan

Capture requests and post new ones to a channel on Starter too. Linear and Jira sync are on Pro and Enterprise.

## Frequently asked questions

### Is the Linear and Jira sync really two-way?

Yes. Moving the issue moves the request, and changes made in Feedovate flow back to the issue through your status mapping.

### Which plan includes integrations?

Linear and Jira sync are on Pro and Enterprise. Slack, the MCP server and the REST API are on every plan.

### Can my AI agent use Feedovate?

Yes. Connect any MCP client and it works with your permissions. See the agents page for setup.
