Sign up

TEAMWORK MCP

Your team and projects.
One MCP.

Full visibility into who’s working on what and where every project stands, across Slack, Jira, Notion, GitHub, etc.

Save 70% of your Claude Code tokens with MCP Context Gateway.

Create your organisationSee how it works

Connect your tools when you’re ready.

WHILE YOU WERE AWAY

Catch up
after a break.

Ask what changed while you were away. See finished work, new decisions, and open threads in one view.

“What did my team do while I was away?”

Choose the team, then see each change by day, connected to the work and conversations behind it.

QUESTIONOUTLINEDASHBOARDEXAMPLE

While you were away

Which team?Mobile DevFront End WizardsPlatform Support
Finished
6
Started
4
Decisions
2

What changed

  • Jane finished validating the milestone
    Jira · ABJAN-3 · Thu 9 Oct
  • Go-live moved two weeks earlier
    Slack · #edge-comms · Thu 9 Oct
  • Omega account plan published
    Confluence · Omega account · Tue 7 Oct
Illustrative dashboard. Generated from the question, with every item connected to its source.
BE THERE FOR YOUR TEAM

Help your team
where it counts.

See what each teammate is focused on and where a hand would help, from the work, documents, and threads you can already see.

“Where could I help my team this week?”

Spot open asks before they stall, and offer help where it moves the team forward.

QUESTIONOUTLINEDASHBOARDEXAMPLE

Your team this week

Who is working on what

  • Rosario
    Replanning the Edge go-live
    Could use a hand
  • Eliza
    Edge Q4 case study
    Waiting on review
  • Tim
    Unicorn integration
    On track

Open asks

  • Rosario asked who can run the CumulusAnalytics demo
    Slack · #edge-comms
    No reply yet
Illustrative dashboard. Generated from the question, with every item connected to its source.
YOUR NEXT TASK

Pick up the
right task next.

Turn open work across your team into a short to-do list, matched to what you know and ranked by what moves the team forward.

“What should I pick up next?”

Each task comes with why it matters now and a link to where it lives.

QUESTIONOUTLINEDASHBOARDEXAMPLE

Your next tasks

To do

  • Prepare the CumulusAnalytics demo

    Not started, and the go-live moved two weeks earlier.

    Jira · ACEDGE-2
  • Answer the Omega requirements question

    Open for three days with no reply.

    Slack · #omega-account
  • Send the forecast inputs to finance

    Requested for Friday.

    Gmail · Account forecast
Illustrative dashboard. Generated from the question, with every item connected to its source.
QUARTERLY REVIEWS

Write reviews
in minutes.

Ask about any time range. See what each person delivered, month by month.

“Summarise my team’s work for Q3.”

Every highlight links to the work behind it, so each review starts from evidence.

QUESTIONOUTLINEDASHBOARDEXAMPLE

Q3 review

Work finished per month

PersonJulAugSepTotal
Rosario43613
Tim34512
Jane25411
Eliza1348

Highlights

  • Rosario led the Edge go-live replan
    Jira · ACEDGE-5 · Sep
  • Tim wrote the Omega requirements
    Confluence · Omega account · Aug
Illustrative dashboard. Generated from the question, with every item connected to its source.
PROJECT TRACKING

Track every
project live.

Generate a tracker with the project’s phases, the people contributing, and their tasks.

“Build a tracker for Project Unicorn.”

It stays current as work moves in Jira, Confluence, and Slack, so everyone sees the same picture.

QUESTIONOUTLINEDASHBOARDEXAMPLE

Project Unicorn

  1. Plan
  2. Implement
  3. Validate
  4. Deliver

Contributors and tasks

  • Tim · Deliver the Unicorn integration
    Jira · ABTIM-3
    In progress
  • Phillip · Implement the milestone
    Jira · ABPHI-3
    In progress
  • Sue · Plan and document the work
    Confluence · Unicorn plan
    Done
Illustrative dashboard. Generated from the question, with every item connected to its source.
MCP CONTEXT GATEWAY

Save 70% of your Claude Code tokens.

The unified memory layer uses 70% fewer tokens than individual calls to your SaaS tools. Bring conversations, code, work, plans, and email into shared context.

Connect your Codex and Claude agents to the MCP Context Gateway. Supercharge them with unified memory to create dashboards across your tools.

BRING YOUR OWN CLOUD

Deploy the gateway and memory layer in your cloud. Connect your sources, then serve your agents the context they need.

Connect your agents
ONE MEMORY. CONNECTED AGENTS.BYOC
Bring your own cloud: unified memory and MCP Context GatewaySlack, GitHub, Jira, Confluence, Gmail and Notion connect through vendor APIs to connectors in your cloud. Connectors feed unified memory. Codex and Claude agents request focused context from the MCP Context Gateway, which retrieves it from unified memory. Agents use this connected context to create dashboards.Bring your own cloud: unified memory and MCP Context GatewaySlack, GitHub, Jira, Confluence, Gmail and Notion connect through vendor APIs to connectors in your cloud. Connectors feed unified memory. Codex and Claude agents request focused context from the MCP Context Gateway, which retrieves it from unified memory. Agents use this connected context to create dashboards.
Sources → unified memory → focused MCP context → agent-created dashboards.
YOUR TEAM, IN CONTEXT

See progress.
Skip the “status update” ping.

Ask your unified memory layer how work is moving. Connect the pull requests, conversations, and tasks behind every project to the people moving it forward.

“What’s Peter’s progress on Project Unicorn?”

See what Peter has shipped, what’s waiting for review, and what needs attention across GitHub, Slack, and Jira.

PEOPLE → PROJECTS → WORKEXAMPLE
Peter’s connected work on Project UnicornPeter connects to Project Unicorn and its GitHub pull request, Slack launch discussion, and Jira issue UNIC-42. The issue is in progress. An example alert below asks to notify you when Peter moves UNIC-42 to Done.Peter’s connected work on Project UnicornPeter connects to Project Unicorn and its GitHub pull request, Slack launch discussion, and Jira issue UNIC-42. The issue is in progress. An example alert below asks to notify you when Peter moves UNIC-42 to Done.
Illustrative project. Every piece of work stays connected to its source.
THE UPDATE COMES TO YOU

Turn a question
into an alert.

Follow the work that matters across your tools. Ask for an update when a task changes status, a pull request needs review, or a conversation needs your attention.

“Notify me when Peter moves UNIC-42 to Done.”

See the change, the project, and the source together. Spend less time checking for updates and more time acting on them.

WATCHCHANGEALERTEXAMPLE

Your team alerts

  • Jira

    Peter moved UNIC-42 to Done

    Connector handover is complete. Your watched work has moved forward.

    PROJECT UNICORN · UNIC-42
    Done
  • GitHub

    Pull request #128 is ready for review

    Project access controls are ready for a second pair of eyes.

    PROJECT UNICORN · PULL REQUEST #128
  • Slack

    Launch handover needs a reply

    Peter mentioned you in the project’s handover discussion.

    PROJECT UNICORN · #PROJECT-UNICORN
Illustrative alerts. Each update stays connected to its project and source.
SECURITY FIRST

Your access is controlled and protected

Your dashboards and alerts draw only from pages you’re allowed to see. Bring your tools together while keeping each person’s access boundaries in place.

Your permissions come with you.

Source permissions define which information can enter your context. Restricted pages stay outside your results.

The same connected workspace. A view shaped by your access.
SOURCE → ACCESS → CONTEXTSECURITY FIRST
Only permitted pages reach your dashboards and alertsAllowed pages pass through a locked access check to dashboards and alerts. Restricted pages stop before the gate. Each viewer sees information within their own source permissions.Only permitted pages reach your dashboards and alertsAllowed pages pass through a locked access check to dashboards and alerts. Restricted pages stop before the gate. Each viewer sees information within their own source permissions.
Access boundaries stay in place as permitted information becomes dashboards and alerts.
LEARN FROM YOUR GRAPH

Turn team knowledge
into training.

Generate step-by-step tutorials on the topics in your knowledge graph. Connect Claude or Codex to turn project pages, team decisions, and runbooks into lessons grounded in how your team works.

“Teach me how releases work on Project Unicorn. Create a tutorial with source links.”

Help new teammates get started, learn a workflow, or understand a project. Keep the sources beside each lesson, and review the guide before sharing it.

TOPICSKNOWLEDGETUTORIALEXAMPLE
GitHubRelease workflow
SlackTeam decisions
NotionProject brief
YOUR PERMITTED GRAPH CONTEXT
TRAINING TUTORIAL

Releases on Project Unicorn

  1. 01

    Understand the project

    Start with the goals and release responsibilities.

  2. 02

    Follow the release workflow

    Walk through pull requests, checks, and handover.

  3. 03

    Put it into practice

    Use the team’s checklist to prepare your first release.

SOURCES · Project brief · Release runbook · Team decisions
Example tutorial structure. Your agent creates the guide from information you’re allowed to see.
GOVERNANCE BY DESIGN

Keep the data
in your own AWS account.

Keep your connected knowledge in your own cloud. Deploy the gateway and unified memory layer in your cloud account, keep access scoped to each project, and review key workspace activity. Your data stays connected to its sources, permissions, and evidence.

A record of who did what.

Review recorded project changes, tool connections, access decisions, and questions in Activity.

Question events record who asked and the outcome. Question text, answers, and credentials stay out of those events.
YOUR CLOUD → ACCESS → EVIDENCE → ACTIVITYGOVERNANCE

Your data, your cloud

Deploy the gateway and unified memory layer in your cloud account, on infrastructure you control.

YOUR CLOUD · YOUR INFRASTRUCTURE

Access stays scoped

Project membership and source permissions define the context you can use.

PEOPLE · PROJECTS · PERMISSIONS

Evidence stays connected

Citation references are checked against the evidence available to the person asking.

SOURCE · DOCUMENT · PASSAGE

Activity stays reviewable

Review recorded actions, their actor, project, and outcome in Activity.

WHO · WHAT · WHEN · OUTCOME
Your cloud, scoped access, source evidence, and recorded workspace activity.

Proven in production

We beat the frontier, on plain Postgres.

Across three public multi-hop benchmarks (MuSiQue, HotpotQA, 2Wiki), our graph engine beats Milvus’s Vector Graph RAG on all three and posts the best average of the field, 88.6 Recall@5, on nothing but Postgres. It traverses the graph in the database and ranks once, not a model call at every step, so answers stay connected to the evidence behind them.

Full benchmarks Read the engineering
3 public benchmarks · avg Recall@5 · n=1000
Ours, graph engine on Postgres
88.6%
Vector Graph RAG (Milvus)
87.8%
HippoRAG 2
87.1%
NV-Embed-v2
80.2%
Naive RAG
73.4%

App marketplace

One graph. Every app.

Install apps from the marketplace, docs, chat, tickets, channels, and the graph keeps them in sync. Or build your own.

SlackSoon
TeamsSoon
NotionSoon
ConfluenceSoon
JiraSoon
LinearSoon
OutlookSoon
+Build your own

Marketplace apps are on the roadmap. Connecting a tool is optional during signup.

Your team and projects. One MCP.

Sign up Book a demo

London · hello@abotcompany.com