A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
METODIC 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.
What it does
Design workshops from chat: 750+ facilitation methods, timed agendas, worksheets, slide decks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http metodic-mcp https://www.metodic.io/mcp
# 2 — ask your agent for something these tools do
# list_frameworks, find_session_format, answer_from_library and 17 more
METODIC costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 metodic-mcp https://www.metodic.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
20 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.
Browse Metodic's learning and facilitation frameworks (Design Thinking, Liberating Structures, 4C/ID, PreMortem and more) with what each is best for and when to use it. Use it to ground a session design in a real methodology rather than a generic structure.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional keyword to filter by name/category. |
START HERE when someone describes a PROBLEM or CHALLENGE ('our leadership team works in silos', 'nobody speaks up in retros', 'we need to align on strategy') and wants a session for it. Returns proven, ready-made session formats from Metodic's catalogue: the problem each one solves, who it is for, how long it runs, what it produces, WHY it works, and the named methodology it is built on. These are
| Parameter | Type | Required | Notes |
|---|---|---|---|
| challenge | string | yes | The problem in the user's own words, e.g. 'departments blame each other instead of solving things'. |
| max_duration | number | no | Optional: longest acceptable session length in minutes. |
| audience | string | no | Optional: who is in the room, e.g. 'executives', 'agile teams', 'teachers'. |
| language | string | no | Optional ISO code (en, nl, es, ja). Defaults to the user's language. |
The answer format for anything the user could pick up and use. ALWAYS use this — not generate_document, not prose, not a web search — for a question about WHAT TO USE OR READ — 'which energizer for a flat afternoon group', 'what learning formats could I run this session as', 'which framework fits a two-day programme', 'give me a case for this topic'. MATCH THE TOOL TO WHAT WAS ASKED. Asked which S
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | no | Optional but STRONGLY preferred when the conversation is about a session: saves this answer to that session's Answers tab in Metodic, so it outlives this chat. Pass it whenever you know which session |
| question | string | yes | The user's question, in their own words — becomes the heading. |
| intro | string | yes | One or two sentences framing your answer: what you went for and why. |
| methods | array | no | Methods you picked, in the order you'd recommend them. |
| framework | object | no | Optional framework to hang it on. |
| formats | array | no | Optional ready-made session formats (slugs from find_session_format). |
| reading | array | no | Optional reading. Use article_slug for a Metodic article; otherwise give title and author and it is shown as an external work. |
| cases | array | no | Optional written cases to put in front of participants — use THIS when the user asks for more than one ('give me three cases'). Each is a short scenario the group works on. This is where a case belong |
| case | object | no | Optional single written case. For several, use cases instead. |
| my_sessions | array | no | Optional: the user's own earlier sessions worth reusing (ids from list_my_sessions). |
| note | string | no | Optional closing caveat or tip. |
Search Metodic's own published articles on facilitation, workshop design and learning. Use this BEFORE reaching for the open web whenever the user asks for sources, background, reading or inspiration: Metodic has its own writing on these subjects, and an article found here can be cited by slug in answer_from_library and saved to the session. Returns slug, title and summary. Free and instant.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords, e.g. 'psychological safety', 'retrospective', 'bias'. |
Search Metodic's library of PROVEN facilitation methods — hundreds of real, tested formats with timing, step-by-step instructions, facilitator tips and materials (plus any the user saved themselves). ALWAYS use this before suggesting an activity, exercise, energiser, icebreaker, ideation format, retro or workshop segment: recommend methods that exist and have been run, instead of inventing one. Fi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Keyword(s) matched against title/description/category, e.g. 'icebreaker', 'prioritise', 'stakeholder'. |
| max_duration | integer | no | Only methods that fit within this many minutes. |
| category | string | no | Optional category filter. |
Turn the conversation into a REAL session in the user's Metodic account: a timed agenda built from the method library, saved and ready to run, edit, share and export. Returns a session_id immediately and the Metodic card fills itself in about a minute — do not poll design_status yourself unless the client has no card. Costs 2 Metodic credits. This is the hand-off from chat to Metodic: after it, of
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | What the session is about (title or subject). |
| duration_minutes | integer | yes | TOTAL session length in minutes, across all days (min 30). For a two-day programme of about 7 hours a day, that is 840. |
| days | integer | no | Number of days (default 1). Set this whenever the user says two-day, three-day, multi-day or an offsite spanning several days — each day then gets its own opening, breaks and closing, and its own cloc |
| participants | integer | no | Number of participants (default 12). |
| goal | string | no | The purpose / desired outcome — pass the user's FULL brief verbatim (context, the client's own vocabulary, the named people and their tensions, the constraints, what must NOT happen). The Architect de |
| audience | string | no | Audience or experience level (e.g. 'beginners', 'leadership team'). |
| format | string | no | e.g. 'workshop', 'training', 'in-person', 'online'. |
| framework | string | no | Optional framework slug/name from list_frameworks. |
| format_slug | string | no | Optional: the slug of a proven format from find_session_format. Seeds the design with that structure and records that the format was used — pass it whenever the user picked one. |
| language | string | no | ISO code (en/nl/es/fr/de/pt/it/ja/zh). Default en. |
Check whether a session started with design_session is ready. While generating it returns a wait instruction; when ready it returns the BRANDED HTML SESSION BRIEF — render it as an artifact. Free (no credits).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session id design_session returned. |
Modify an existing session's agenda IN PLACE without leaving the chat: retime, rename, move, remove or update activities, or add new ones. Put EVERY change the user asked for in ONE call — a second call paints a second full session brief and the user sees the agenda twice. Give a list of operations; they apply in order, and activity numbers are 1-based positions in the agenda AS IT STANDS after an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
| operations | array | yes | Changes to apply, in order. Shapes: {op:'retime', activity, duration_minutes} · {op:'rename', activity, title} · {op:'remove', activity} · {op:'move', activity, to} · {op:'update', activity, descripti |
READ a session so YOU know what is in it before answering a follow-up — this returns text for you, not something the user sees. To SHOW the session to the user, call session_one_pager instead. Gives every activity's agenda slot, method, step-by-step instructions, facili — every activity's agenda slot, method, step-by-step instructions, facilitator tips and materials. Plus a Metodic link for the br
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
Return a complete, self-contained, Metodic-BRANDED HTML one-pager of a session (logo, brand colours, agenda table, activity cards). RENDER THE RETURNED HTML AS AN ARTIFACT so the user sees the branded document. Use for the FULL session overview: the agenda with activity detail, for the facilitator or for stakeholders who want to see the whole design. FREE (no AI, no credits). For a written documen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
NOT for a list of sources, methods, formats or reading — that is answer_from_library, which draws on Metodic's own library and saves the result to the session. Use this only for a WRITTEN DOCUMENT with its own audience: a pre-read, a briefing, a client brief, prep notes, an invitation, a follow-up. Creates it with Metodic's real document builder (the same 'Documents' generator as Metodic's Materia
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
| title | string | yes | Document title, e.g. 'Pre-read for participants'. |
| purpose | string | yes | What the document is for and what it must achieve, in 1-3 sentences. |
| force | boolean | no | Only when the user explicitly wants a separate sendable document that happens to contain cases. Without it, a request for cases is redirected to answer_from_library, where it is saved to the session. |
| audience | string | no | Who reads it: participant (default), facilitator, or client/sponsor. |
| content_spec | string | no | Optional: what it should contain / structure / things to include or deliberately leave out (e.g. 'no method names — keep the exercises a surprise'). |
List the user's recent Metodic sessions with links.
No parameter schema on file.
Create a shareable link to a session so someone else can see it WITHOUT a Metodic account: a client or sponsor who has to approve the programme, a co-facilitator, or the participants. Optionally writes a client-facing brief first (audience 'client') and shares that alongside the plan. Returns the link. Reuses an existing link for the same session instead of making a second one. Free unless a brief
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | Metodic session id. |
| audience | string | no | Who the link is for. 'client' is the default and the most common: a sponsor who must approve it. |
| with_brief | boolean | no | Also write a short client-facing brief for the session (costs ~0.5 credit). Default false. |
| document | string | no | Which saved document opens on the shared page: 'latest' (default for a client — the most recent document in the session, e.g. a brief you just wrote), 'none' for the plan only, or a document id. |
| expires_in_days | integer | no | Optional: let the link expire after this many days. |
Show the user's available Metodic credits (the balance that generation tools spend — for team members this is the team's shared balance). Call when the user asks about credits, cost, or whether they can afford a generation.
No parameter schema on file.
Save a post-session DEBRIEF onto the session in Metodic: how it went, what worked, what to improve, follow-ups. Call after the user has run their workshop and tells you how it went (or after a debrief conversation) — synthesize first, then save. Debriefs accumulate on the session; nothing is overwritten.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
| notes | string | yes | The debrief synthesis — how the session actually went. |
| went_well | array | no | Things that worked. |
| to_improve | array | no | Things to change next time. |
| follow_ups | array | no | Actions owed after the session. |
| rating | integer | no | Overall 1-5. |
Generate the A4 PARTICIPANT WORKSHEET for ONE activity — the sheet each participant fills in on their own, at the table. NOT the big sheet on the wall: if the user says canvas, wall canvas, poster, brownpaper, large format, A1, A0, matrix or mapping wall, use generate_canvas instead. Uses Metodic's real generator and returns a branded document in the chat (also saved to the session for the print-r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
| activity | integer | yes | The activity's number in the agenda (1-based). |
| regenerate | boolean | no | Only set this to true when the user explicitly wants a NEW version. Left out, an existing one is returned as-is and costs nothing. |
THE TOOL FOR ANY CANVAS. Generate the large-format WALL CANVAS for ONE activity using Metodic's real canvas generator, and return it as a branded document in the chat (also saved to the session, and replayable 1:1 to a Miro board). This is the big thing that goes ON THE WALL and that a group fills in together — sized to who shares it (one A1 for the whole room, an A2 per small group) — as opposed
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session id. |
| activity | integer | yes | 1-based activity number from the agenda. |
| regenerate | boolean | no | Only set this to true when the user explicitly wants a NEW version. Left out, an existing one is returned as-is and costs nothing. |
| canvas_type | string | no | Optional canvas shape. Metodic has ready-made ones: swot, empathy-map, stakeholder-map, business-canvas, priority-matrix, decision-matrix, journey-map, reflection. Anything else (or leaving it out) ma |
| size | string | no | Print size. Leave it on auto: the canvas is A1 when the whole room shares it and A2 when each small group gets its own. Only set it when the user asks for a size. |
Generate a participant HANDOUT or reference material for ONE activity using Metodic's real generator, and return it as a branded HTML artifact in the chat (also saved to the session). Unlike a worksheet (which participants fill in), a handout is READING/REFERENCE material the participant keeps beside their worksheet — background, a framework, a case study, a persona, a checklist. Give the activity
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
| activity | integer | yes | The activity's number in the agenda (1-based). |
| kind | string | no | What kind of reference material to make. Default: handout. |
Generate the session's SLIDE DECK with Metodic's real generator — the same facilitation deck the Metodic app makes: an opening, the day's journey with real times, per activity a chapter, the task (steps, who with, what you make, what you need) and a timer bound to its minutes, breaks with the real return time, live questions, and a closing, all with speaker notes. Shown in the chat as a slide view
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id. |
Generate a METHOD CARD DECK for the session using Metodic's real generator, and shown in the chat as Metodic's paper cards (category post-it colours, icon on the front, steps and a tip on the back; tap a card to turn it). Also saved to the user's decks. One call makes the whole deck. Takes ~30-60s and ~2 Metodic credits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The Metodic session (toolkit) id to base the deck on. |
| count | integer | no | Roughly how many cards to aim for (e.g. 8-16). Optional. |
- 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 METODIC or to call it, at any volume.
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.
No release note was published with this version.
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.
Any signed-in account that does not publish METODIC can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.