servers / noemic
Noemic MCP server
communitystreamable_httpremotedestructive capablehealthy
Someone to talk to, for your user: coaches, mentors, accountability partners. First session free.
01Tools · 47
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| get_started Call this FIRST when a user has just connected or is unsure what Noemic is. Returns the honest state of the marketplace and the four paths. Present them as 2-4 tappable choices, not prose. | read | false | unknown |
| register For a NEW user: create their Noemic account with an email and a password they choose, and get back a sessionToken to use for the rest of the conversation. Ask the user for a password (8+ chars) they'll remember — it also logs them into noemic.app. If the email already has an account, this fails and you should use login instead. Return the token to yourself only; never read it aloud. | read | false | unknown |
| login For a RETURNING user: verify their email + password and get back a sessionToken to use for the rest of the conversation. If they've never set a password, use register instead. Wrong credentials return a single generic error (no account enumeration). Never read the token aloud. | read | false | unknown |
| logout Invalidate a sessionToken (e.g. on a shared device). After this the token no longer works and you must login again. | unknown | unknown | unknown |
| match_me The SHORTCUT, not the primary move: a server-side keyword pre-ranker for when list_people is too long to read in full (it isn't yet) or you need one fast shortlist. Prefer list_people + your own reading — you understand meaning; this ranks tokens. Results carry availableNow, freeFirstSession, and next opening. If the user needs support NOW, lead with availableNow people and book_now — connecting to in-session should take under five minutes. Present a MIX of free-first and paid options so the user genuinely chooses. | read | false | unknown |
| list_people THE PRIMARY DISCOVERY MOVE: you are the matcher. Optionally narrow by formal facts (price of entry, presence, an opening soon — never categories), then READ every story and corpus that comes back and decide who actually fits your user. At today's marketplace size the full read always fits; prefer this over match_me, and present a small panel mixing free-first and paid options. | read | false | unknown |
| get_person Full profile (story + corpus) for one person by profile id. | read | false | unknown |
| get_availability Open (unbooked, future) slots for a person, soonest first. | read | false | unknown |
| book_session Book an open slot with a person. Pricing is automatic: first-ever session on the platform is free; otherwise an available session credit auto-redeems; otherwise the pro's self-set rate is charged. The result states what was paid — tell the user. | write | true | unknown |
| book_now Instant session with someone whose availableNow is true: the booking starts immediately and the result carries the roomUrl — send the user straight in. Same pricing as book_session (free first session where offered, then credits, then the prorated rate — state the price first). Default 30 minutes. | write | true | unknown |
| set_available_now Pro-side presence has TWO parts: this controllable status (open/closed) AND recent activity — a pro shows as available-now only while their status is open AND they've been active in the last 15 minutes (their dashboard heartbeats while open; calling this tool also counts as activity). So: open it when the pro is genuinely at their desk, and if they stay only agent-side, re-call it within every 15 minutes to stay live. Available-now pros rank higher for urgent needs and are bookable via book_now. | write | true | unknown |
| complete_session Call after a session actually happened. The PRO earns a session credit they can spend as a client (the loop that keeps Noemic alive) and their quality record grows. | unknown | unknown | unknown |
| cancel_booking Cancel a confirmed booking: any charge is refunded, a redeemed credit is returned, and the slot reopens. | destructive | true | true |
| my_bookings Bookings as client and as pro, soonest first. | unknown | unknown | unknown |
| become_available Create the user's profile so others can book them. Draft everything from your conversation — their words, their experiences, what they'd be good at being in someone's corner for — and confirm with them before calling. No credentials needed, no review queue: the only qualification is being human. Rate is self-set (0 or omitted = free/credits-only; they earn a credit per session they run either way). Include availability if they told you when they're free. | unknown | unknown | unknown |
| my_profile Status probe: does the user have a profile, what's missing to make it bookable, plus credits, upcoming sessions, and active commitments at a glance. Call this before assuming anything about the user's state — cheaper than asking them. | read | false | unknown |
| add_availability Add open session slots to the user's profile. endsAt defaults to one hour after startsAt. | write | true | unknown |
| add_to_my_corpus Append text to the user's agent-readable corpus (with their consent). Anything that would help future matching: new experiences, what a session with them is like, boundaries, wins from sessions they ran. Append-only and date-stamped. | write | true | unknown |
| update_my_profile Update display name, headline, story, rate, or listing/visibility flags. | write | true | unknown |
| create_commitment The user stakes real money on doing a specific thing by a deadline. Succeed → refunded; fail → forfeited. Make the title concrete and checkable ('run 3x this week', not 'exercise more'). Follow up with the user before the deadline. Server-enforced cap: at most $500 of active stakes per user; the result reports remaining headroom. | write | true | unknown |
| resolve_commitment Resolve an active commitment: succeeded → stake refunded; failed → stake forfeited. Self-report — ask the user directly and record their answer honestly. | unknown | unknown | unknown |
| my_commitments All commitments with status and deadlines (active first). Check for approaching deadlines worth nudging about. | read | false | unknown |
| session_transcript The consent-gated transcript of a session in the platform room. Participants only. During a LIVE session, poll with sinceMs set to the atMs of the last segment you saw (only newer segments return). Use it to supervise: understand where the conversation is, then send_cue when one would help. | unknown | unknown | unknown |
| send_cue Pro-only, during a live session. The cue appears quietly in the pro's room panel — the client never sees it. Discipline: ONE short cue (max 25 words), specific to what was actually said — a question worth asking, a dropped thread, a reminder to listen, a concrete next step. Silence is fine; never send generic advice. | write | true | unknown |
| write_debrief Pro-only, after a session. Read the full transcript first (session_transcript), then write honestly and specifically, referencing actual moments: strengths = 2-3 things that worked; growth = the single most important thing to do differently and where it mattered; drill = one concrete exercise before the next session. One debrief per session; it feeds the pro's quality record and their my_coaching history. | write | true | unknown |
| session_debrief After a session ends, the pro gets a private AI debrief (what worked, what to change, a drill to practice). Pro-only: the email must be the session's pro. Use it to help your user prepare for their next session. | unknown | unknown | unknown |
| my_coaching All AI debriefs from sessions the user ran as the pro, newest first — their private improvement record. Read it before their next session and coach them on the recurring growth themes. This is how someone new gets good fast. | read | false | unknown |
| file_brief The demand side is a filed document, not a search: write what your user needs (a few real sentences — situation, what kind of person would help, cadence they want) and it stands, anonymous to pros, converging with new people as they join. Returns today's matches immediately. Check my_briefs on later visits. | read | false | unknown |
| my_briefs All briefs with matching re-run against today's marketplace plus any intros received. Call when your user returns — new people may have joined since the brief was filed. | read | false | unknown |
| open_briefs Open briefs, anonymous (the need, never the person). For the supply side: show a pro what demand exists, or a hesitant would-be pro that people are already waiting for someone like them. Reach toward one with send_intro(briefId). | read | false | unknown |
| close_brief Close an open brief (found someone, or the need passed). | unknown | unknown | unknown |
| send_intro Send a short real intro through the platform (no emails exposed). Two directions: profileId — your user reaching toward a person whose story fits; briefId — your user (who has a profile) reaching toward an open need. Acceptance creates a connection. | write | true | unknown |
| my_intros Pending intros addressed to the user. Respond with respond_intro. | unknown | unknown | unknown |
| respond_intro Accepting creates the CONNECTION — the standing relationship where messages, sessions, artifacts, and witnessed commitments live. If your user is the client side, immediately port_context so their person knows exactly what is going on. | unknown | unknown | unknown |
| port_context Client-side only, with the user's consent: write the full situation into the connection — what is going on, history, what has been tried, what they want — so their person starts knowing everything. Replaces the intake interview. Update it as things evolve; the pro and their agent read it. | read | false | unknown |
| my_connections Every connection: who, context brief, last message, active witnessed commitments. The relationships you are responsible for keeping alive. | unknown | unknown | unknown |
| send_message Async relay between the two people (agents deliver both ways). The daily two-line check-in lives here — cadence beats duration. | write | true | unknown |
| check_messages The heartbeat: call whenever your user shows up. Returns unread messages from all their connections (marked delivered). Relay them in the person's own words. | read | false | unknown |
| create_artifact Pro-side: design an interactive exercise ONCE (thought record, weekly review, values check — see coaching_playbook topic artifact_patterns). The script is instructions a client's agent follows to run it conversationally. Public artifacts join the shared library. | write | true | unknown |
| artifact_library Public artifacts from all pros, ranked by real adoption. Search in plain language ('procrastination', 'reframing', 'weekly accountability'). Assign any of them — assigning from the library is how good exercises spread. | read | false | unknown |
| my_artifacts Artifacts this pro designed, with adoption counts. | unknown | unknown | unknown |
| assign_artifact Pro-side: assign an artifact (yours or from the library) to a client, with an optional note. Best moment: as a session lands, one artifact at a time. The client's agent administers it and the result comes back into the connection. | write | true | unknown |
| my_assignments Client-side: pending exercises assigned by the user's people. Run each script conversationally at a good moment — you are the facilitator — then complete_assignment with the substance of what emerged. | unknown | unknown | unknown |
| complete_assignment After administering an assigned exercise: post back what the script asked for. The result lands in the connection where their person (and their person's agent) sees it. | unknown | unknown | unknown |
| coaching_playbook The curriculum you coach your pro with: active_listening, powerful_questions, cbt_basics, motivational_interviewing, accountability_structures, session_structure, boundaries_and_referral, artifact_patterns. No topic returns the index. Ground your cues, debriefs, and artifact designs in this. | read | false | unknown |
| set_password Lets an account created over MCP claim its web dashboard (noemic.app/login): profile, connections, assignments, session rooms. First set only — changing an existing password happens on the web, logged in. | write | true | unknown |
| my_credits Unredeemed session credits (earned by running sessions). They auto-redeem on the next paid booking. | unknown | unknown | unknown |
02Install & source
https://noemic.app/mcp
remote_url03Access granted
Read calendar · writeSend chat messages · writeGenerate images · write
The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-07-17 05:40Z
next_check2026-07-19 05:40Z
cadenceevery 48h
verifiedtools_list:passed handshake:passed metadata:failed
index_statusindex — 6 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README. 
[](https://mcpexplorer.com/servers/noemic)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →