MCP connection

Connect your AI to your Anivia team over MCP. Ask Claude Code, Codex or Cursor for help while you work, and it writes the brief, attaches the files and puts the task on our board. No call, no PRD, no approval round.

The old agency way
EmailDiscovery callPRDEstimateApproval
Days of back-and-forth before anyone designs a thing
Anivia MCP
/aniviaTask on the board
Your AI writes the brief while you keep working

Context comes with it

Your AI has the code open, so the task arrives with the page, the files, the stack and what is wrong. Nobody has to ask.

No document to sign off

The brief is the task. Change its priority or wording on the board, but there is no PRD to write and approve first.

Stay where you work

Ask your AI what's new, read the team chat or check a task without opening another tab.

How it works

Type /anivia and say what you need. Your AI checks your workspace, reads the files involved and writes the task: goal, where it lives, the current state and what done looks like.

The task lands in the Backlog of your Anivia board and a design engineer picks it up. Later, ask your AI for updates or the team chat and it reads them for you.

The connection

  1. 01

    You and your AI

    You type /anivia and what you need, right where you work.

    • Claude Code
    • Codex
    • Cursor
  2. 02

    Anivia MCP server

    Your AI calls our tools with your personal key.

    • get_project
    • list_tasks
    • create_task
  3. 03

    Your Anivia board

    The task lands in Backlog with the brief and the files.

    • Board
    • Chat
    • Files
  4. 04

    Your Anivia team

    A design engineer picks it up and ships a preview.

    • Design engineer
    • Developer

And back. Status changes, comments, chat and preview links come back the same way. Ask /anivia what's new? and your AI reads them with get_updates and read_chat.

What's included

  1. 01

    Create tasks

    A title, a structured brief and the key files attached, written from what you are working on.

  2. 02

    Check the board

    List open tasks and their status, so it adds to an existing task instead of making a duplicate.

  3. 03

    Get updates

    Status changes, team comments and chat since you last asked, in one answer.

  4. 04

    Read the team chat

    Catch up on what your designer or engineer said without leaving your editor.

  5. 05

    Comment and reply

    Post a comment or a chat message, only when you ask it to and with the text you approved.

  6. 06

    Keep secrets out

    The /anivia instructions tell your AI to drop .env files, keys and tokens before anything is sent.

Anivia MCPOld agency workflow
Starting a requestAnivia MCPOne message in your editorOld agency workflowEmail, then a call
The briefAnivia MCPWritten by your AI from the codeOld agency workflowA PRD you write and approve
ContextAnivia MCPFiles, routes and stack attachedOld agency workflowScreenshots and a call recording
ApprovalsAnivia MCPNone, it goes to the queueOld agency workflowEstimate, sign-off, kickoff
UpdatesAnivia MCPAsk your AI "what's new?"Old agency workflowA weekly status meeting
  • Claude Code
  • Codex
  • Cursor
  • Windsurf
  • Claude Desktop
  • VS Code
  • Any MCP client
FAQ

All questions

The Model Context Protocol is an open standard that lets AI assistants use outside tools. Our MCP server gives your AI a small set of tools for your Anivia workspace: read the project and board, create tasks, get updates and read the chat.