Integrations

Wire Project Feed into the rest of your stack

A REST API that covers every primitive, signed webhooks for events, a typed CLI for scripts and CI, and a built-in MCP server so agents can work the same surfaces your team does.

Start free

REST API

Every primitive behind one clean API

Posts, tasks, docs, comments, and members all sit behind a documented REST API. OpenAPI 3.1, cursor pagination, idempotency keys, and problem-detail errors that follow RFC 9457, so the client you generate actually behaves.

POST /v1/posts

201 Created

curl -X POST https://api.projectfeed.app/v1/posts \
  -H "Authorization: Bearer pf_live_9f2c…" \
  -H "Idempotency-Key: 7b41-d20a" \
  -d '{ "projectId": "web", "body": "Shipped v2" }'

# 201 Created
{ "id": "post_8fa2", "url": "…/p/8fa2" }

Built to connect

Events, agents, and chat

Push changes out the moment they happen, let agents call the same tools your team uses, and keep the discussion flowing into the channels people already watch.

post.created200

sha256=4a1f…e9c2

Signed delivery, retried on any 5xx.

Signed webhooks. Subscribe to any event, verify the HMAC signature, and lean on retries with a dead-letter queue behind them.

MCP server

12 tools for agents

create_postsearch_taskslist_docs

An MCP server for agents. Point Claude or any MCP client at your workspace and it reads and posts through the same permissions you have.

web-updates

Project Feed bot

New post from Dana: Deploy done ✅

Routed to Slack and Discord.

Slack and Discord. Route posts and mentions to the channels people already check, with replies landing back in the feed.

CLI

Script it straight from the terminal

Install pfeed-cli, run pf, and drive the whole API from your shell or a CI job. Create a post on deploy, file a task from a failing test, or pull a project's activity into a report.

zsh · pfeed-cli

$ pf posts create --project web --body "Deploy done"
✓ Created post PRO-1287

$ pf tasks list --status in_progress
PRO-1290  Require MCP OAuth grants
PRO-1293  Retain blocked storage rows

$

Attribution

See what posted each update

Anything created through the API, the CLI, an agent, or a chat bot carries a small icon of what made it. An agent's post never reads as a teammate's, and an API write names the client that sent it right down to the key.

Blitz· activity

Maya Chen

Shipped the boss arena pass

Sam PatelClaude

Filed 3 tasks from the crash report

Release botCLI

Build #482 is live

Priya AnandCursor

Refactored the spawn timing

Dana ColeSlack

Can we push launch to Friday?

Attribution

Created via Claude

on Sam Patel’s key

API key: ci-bot
Token: pf_live_9f2c…
Wrote: POST /v1/tasks ×3
When: 2m ago

Posts from the app stay unmarked.

Pairs with

Better together with the rest of the workspace

Feed

Every update, comment, and file on one chronological project timeline.

Analytics

Honest team insight from real activity, shared with the whole team for context and health.

Docs

A real-time block editor with comments and version history, pinned to the project.

Build on an API that holds up

REST, webhooks, CLI, and MCP, documented and ready. Free to start, no card needed.

Start free