A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Memoket is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Memoket — access your recording transcripts, summaries, and key takeaways over MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http memoket-mcp https://mcp.memoket.ai/mcp
# 2 — ask your agent for something these tools do
# search_recordings, get_conversations, get_transcripts_by_participant and 4 more
Memoket costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MMAll 1 server
mcp.memoket.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http memoket-mcp https://mcp.memoket.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
[search] Unified recording search. Runs bounded searches over transcript lines, topic segments, memory atoms, participant metadata, titles, briefs, summaries, and action items in one call. Returns typed hits plus conversation_ids, line_ids, segment_ids, memory_atom_ids, participant_ids, brief_ids, summary_ids, action_item_ids. Chat execution expands hits into readable evidence automatically; exter
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | no | Optional: restrict to these opaque recording ids. |
| end_time | string | no | ISO 8601; filters by recording started_at. |
| query | string | no | Required. One phrase for a single concept, or a JSON array string of 2-4 distinct facets. |
| search_types | array | no | Optional lane filter. Omit to search all. Allowed: transcript, segment, memory_atom, participant, title, brief, summary, action_item. |
| start_time | string | no | ISO 8601; filters by recording started_at. |
[metadata_query] Conversation-level metadata for the given conversation_ids: id, title, started_at, ended_at, duration_seconds, participants, language_code. No transcript, brief, or summary body.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | no | required, non-empty; opaque recording ids |
[content_fetch] Transcript lines associated with participant_ids in conversation_ids. Turns participant metadata into transcript evidence for exposed search results.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | no | recording ids scoped by participant hits |
| limit | integer | no | — |
| participant_ids | array | no | participant ids from search_recordings.participant_ids |
| query | string | no | — |
[content_fetch] Per-conversation compact report body for the given conversation_ids using Brief -> Summary -> Standard, where Standard is the first completed non-empty type=0 report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief_ids | array | no | optional brief ids from search_recordings.brief_ids |
| conversation_ids | array | no | recording ids from brief hits |
| offset | integer | no | — |
[content_fetch] Per-conversation summary body. With summary_ids, fetch exact summary reports from search_recordings. With conversation_ids only, fetch the latest summary report for each conversation. Paginated (offset).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_ids | array | no | required, non-empty; ids are opaque strings (may be 19-digit snowflake) |
| offset | integer | no | — |
| summary_ids | array | no | optional summary ids from search_recordings.summary_ids |
[content_fetch] Verbatim transcript of ONE recording by conversation_id. Paginated (offset / next_offset) — page through for more.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| conversation_id | string | no | required; opaque id string (may be 19-digit snowflake) |
| offset | integer | no | — |
[metadata_query] List recordings by time window / participants. Returns id, title, started_at, ended_at, duration_seconds, participants, language_code (no content). Paginated (count default 100, max 200; offset). order_by ranks within the window. NOTE: participants are speaker labels — placeholders ('Speaker A/B') unless the user tagged them, not necessarily real names.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| count | integer | no | page size (default 100, max 200) |
| desc | boolean | no | true = descending (default); false = ascending. |
| end_time | string | no | ISO 8601, filters on started_at |
| offset | integer | no | page offset; use the response's next_offset |
| order_by | string | no | duration_seconds | started_at | action_item_count — server sorts the whole window and returns the top count. |
| participant_names | array | no | Exact participant filter (may return 0 for un-tagged/anonymized people). |
| start_time | string | no | ISO 8601, filters on started_at |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Memoket or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Memoket can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.