Skip to main content
Use Circleback’s remote MCP server to let Notis read your meeting notes, transcripts, and action items, so you can ask about a past call from whichever channel you happen to be in.

​
What this setup does

Circleback takes meticulous meeting notes. The problem with meticulous notes is that they live in another tab — and the decision you need is usually needed while you are walking to the next meeting. Connecting Circleback’s MCP server to Notis makes your meeting corpus searchable from WhatsApp, iMessage, Telegram, email, Voice Mode, or a coding agent, next to everything else Notis can reach.
Circleback answers “what did we decide?”. Notis answers “find what we decided and do something about it.” The second one is where the time actually goes.

​
Prerequisites

  • A Notis workspace with access to custom MCP connections
  • A Circleback account with a few recorded meetings
  • A browser available to complete Circleback’s sign-in

​
Circleback MCP connection details

Circleback publishes a hosted remote MCP server. Nothing to install, nothing to run locally, and no API key anywhere in the setup.
Server URL: https://circleback.ai/api/mcp Transport: streamable HTTP Auth: OAuth with dynamic client registration
The server exposes read-only search tools over what Circleback knows, including meeting search, meeting reading, transcript search, transcript retrieval for specific meetings, and action-item search, plus calendar and email search.

​
Step 1: Add Circleback as a custom MCP in Notis

  1. Open the Notis Portal and go to Settings → Integrations → Custom MCP.
  2. Click Add MCP.
  3. Name: Enter Circleback.
  4. Description: Give Notis context on when to use it. For example:
“Use Circleback to search my meetings, transcripts, action items and attendees from past calls.”
  1. Server URL: Paste the hosted endpoint:
https://circleback.ai/api/mcp
  1. Authentication: Complete Circleback’s sign-in when Notis prompts you. No API key is required.
  2. Click Save.
Or set it up from any conversation instead:
Notis saves the connection and handles the sign-in flow. Because it uses OAuth, you can revoke the connection on its own at any time without touching anything else.

​
Step 2: Verify the connection

Notis lists the tools the Circleback server exposes once the connection is saved. Try a search you can check by hand:
Search my Circleback meetings from last week and list who attended.
If nothing comes back, re-open the connection in Settings → Integrations and finish the sign-in — an interrupted flow leaves the server connected but unauthorized.

​
Step 3: Ask your meetings something

From WhatsApp, voice, email, or the desktop app:
  • “What action items do I still owe from this week’s meetings?”
  • “Search my meeting transcripts for the conversation about the Q3 budget.”
  • “Who did I meet from Acme last month, and what did we agree on?”
  • “Find the exact thing the customer said about onboarding in yesterday’s call.”
Notis picks the right Circleback tool — action-item search, transcript search, meeting lookup — and answers in the channel you asked from.

​
Example workflow: the pre-call brief

  1. Ask for the history — “I’m meeting Sarah at 3pm. Summarise our last two calls from Circleback.”
  2. Add the present — “Now check my inbox for anything recent from her.”
  3. Get talking points — “Suggest three things I should cover, and flag anything we promised and haven’t delivered.”
  4. Capture afterwards — Send a voice note after the call and let Notis file the follow-ups.
Circleback provides the history. Your other integrations provide everything else.

​
Read, or read and write?

The MCP tools are read-only by design. Notis can search and summarise, but it will not create, edit, or delete anything in Circleback. If you want finished meetings to push work into Notis automatically — tasks created, notes filed, drafts written — that is a webhook automation rather than an MCP connection. See Manage Meetings for the capture side of the workflow.

​
Troubleshooting

  • No tools listed: Re-open the Circleback connection in Settings → Integrations and complete the sign-in again.
  • Empty results: Circleback’s search covers meetings recorded on your account. Check the meeting exists in Circleback first.
  • You want data flowing the other way: The MCP is read-only. Use an automation for push-based workflows.
  • Using it from a coding agent: The same connection is available through the Notis CLI and MCP, so Claude Code or Cursor can pull meeting context while it works.

​
Summary

Circleback’s hosted MCP server connects to Notis with one URL and a browser sign-in. Meeting notes tools solved capture; this solves retrieval — your entire meeting history behind a message, next to your inbox, your calendar, your tasks, and every other tool Notis holds.