Connecting AI assistants

Every includes an MCP (Model Context Protocol) server, which lets you connect AI assistants like Claude directly to your workspace. Once connected, you can ask your assistant about your tasks, log time, check retainer budgets, and more, all in plain language, without leaving the conversation.

What you can do

Your assistant gets a set of tools for working with Every on your behalf:

Tasks

  • Find and search tasks: "what's on my plate this week?", "show me overdue tasks for Globex"
  • Read full task detail, including comments, checklists, and linked git branches and pull requests
  • Create tasks: "create a task for the homepage banner under the TMX project, due Friday"
  • Update tasks: change status, priority, due dates, and assignees
  • Add comments, including @-mentions that notify your teammates

Time tracking

  • Start and stop a timer: "start a timer on GO-6", "stop my timer, I was fixing the checkout bug"
  • Log time directly: "log 2 hours on ST-1 for yesterday"
  • Review your logged time: "how much time have I tracked this week?"

Reporting

If your role has access:

  • Retainer budgets and health: "which retainers are at risk this month?"
  • Team capacity and workload: "who has spare capacity next week?"

Everything the assistant does works exactly as if you did it yourself in Every: tasks it creates are attributed to you, automations fire as normal, mentioned teammates are notified, and it can only ever see the clients, projects, and tasks that you can see. Private work stays private.

Connecting Claude

You'll need the MCP server address for your Every site. It's your site's address on onevery.io with /mcp on the end:

https://your-site.onevery.io/mcp

Claude (web and desktop)

  1. Go to Settings → Connectors in Claude.
  2. Choose Add custom connector and enter the MCP server address above.
  3. Claude opens Every's sign-in page in your browser. Sign in as you normally would.
  4. Review the authorisation screen and choose Authorise.

That's it. Every's tools now appear in Claude's tool menu, and you can start asking questions.

Claude Code (terminal)

claude mcp add --transport http every https://your-site.onevery.io/mcp

Then run /mcp inside a Claude Code session and follow the sign-in prompts in your browser.

Other MCP clients

Any MCP client that supports HTTP transport with OAuth can connect using the same address. The sign-in flow is standard OAuth, so no API keys need to be copied around.

Things worth knowing

  • The assistant is you. It acts under your account and your permissions. If your role can't create tasks or view retainers, neither can your assistant.
  • One timer at a time. Like in Every itself, you can only have one running timer. The assistant will tell you if a timer is already running and on which task.
  • Drafts stay private. Draft tasks are only visible to you, and time can't be tracked against them. Tasks your assistant creates are published (visible to the team) unless you ask for a draft.
  • Task references work naturally. Refer to tasks the same way you do with teammates ("GO-6", "TMX-12") and the assistant will find them.
  • Durations are flexible. Say "90 minutes", "1h30m", or "2 hours". They all work.

Disconnecting

To revoke an assistant's access, go to Settings → Connected Apps in Every and choose Revoke next to the connection. The assistant loses access immediately; nothing it created is affected.

You can reconnect at any time by repeating the steps above.

For administrators

  • The MCP server is controlled by the MCP_ENABLED environment flag. When it's off, the endpoint doesn't exist, and connections and sign-ins will fail with "not found".
  • Connections authenticate through Every's standard OAuth flow (Passport). Each user authorises individually and every action is attributed to the authorising user. There is no shared service account.
  • Tokens issued through the connect flow expire on the same schedule as other API tokens and can be revoked per user from their Connected Apps page.

Was this page helpful?