Semble logoMCP server · Work management

Semble MCP server

Semble in any MCP client, through Memtro: Semble does not publish this server. Memtro's Semble connector reads Semble through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Semble clinic management: appointments by date or by when they changed, with practitioner, location, appointment type and status; practitioners; bookable availability slots; the practice and its locations. When asked, books, moves or cancels an appointment for a patient by id, texts or emails a patient by id, and adds, changes or deletes internal staff tasks. Never reads a patient's record, notes or details.

Reads

  • semble_list_bookingsAppointments in Semble: start and end, status, practitioner, location, appointment type and length, reference and whether billed.
  • semble_list_practitionersStaff in the Semble practice: id, name, whether a clinician, specialties, qualifications and position.
  • semble_availability_slotsFree appointment slots in Semble for practitioners, rooms or locations over at most 14 days, in the practice's local time.
  • semble_get_practiceThe Semble practice: name, timezone, specialties and its locations and rooms (id, name, location group and status).

Acts, when you ask

These change something in Semble. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • semble_create_taskAdd an internal task in Semble assigned to a member of staff (find their id with semble_list_practitioners, include_non_clinical for admin staff).
  • semble_create_bookingBooks an appointment in Semble for a patient, by the patient's Semble id, with a practitioner at a location for a start and end time.
  • semble_update_bookingChanges a Semble appointment: moves it to a new start and end, changes the practitioner, room, appointment type, status or comments.
  • semble_cancel_bookingCancels (deletes) a Semble appointment, freeing the practitioner's time.
  • semble_send_patient_smsSends an SMS from the practice to a patient, by the patient's Semble id, to the mobile number on their record.
  • semble_send_patient_emailSends an email from the practice to a patient, by the patient's Semble id, to the address on their record.
  • semble_update_taskChanges an internal Semble staff task: its subject, comments, priority, due date, assignee, status (open, processing, closed) or general/admin type.
  • semble_delete_taskPermanently deletes a Semble staff task.

Connect it

First connect Semble on Dashboard → Connections, then add Memtro to your client once. The Semble tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Semble connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › What does Dr Ruiz have tomorrow?
  • › When is the next free physio slot?
  • › Which appointments changed since yesterday?
  • › Move Thursday's 10am with Dr Ruiz to 2pm the same day.
  • › Create a task for the practice manager to check Thursday's room bookings.

Questions

Is this an official Semble MCP server?
No. It is Memtro's MCP server with Memtro's Semble connector behind it: the connector reads Semble through its API with the credentials you connect on Dashboard → Connections, and Semble publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Semble?
Only when you ask, and only what it has been granted: create an internal task assigned to a member of staff, with no patient attached; change, reassign or close an internal staff task; delete an internal staff task; book an appointment for a patient by id with a practitioner, room and appointment type; move or change an appointment: time, practitioner, room, type, status or comments; cancel an appointment, optionally telling the patient and emailing the practice; send an SMS to a patient by id; send an email to a patient by id. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time