moa

codes.moaPublished by moa.codesOfficial publisherv1.0.0Updated Oct 28, 2026

Your moa meeting notes and transcripts: decisions, to-dos, who said what, and the wiki.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that gives an assistant access to your moa meeting notes and transcripts, including decisions, to-dos, speakers and the wiki.

What you can do
  • Retrieve meeting notes and transcripts from your moa workspace.
  • Look up decisions and action items recorded in meetings.
  • See who said what in a conversation.
  • Read and reference the workspace wiki.
  • No individual tools are listed, so exact operations are not documented.
When to use it
Useful when you want an assistant to recall what was decided or assigned in past meetings, or to pull context from your team's moa notes and wiki while drafting follow-ups or summaries.
Requirements
A remote endpoint at mcp.moa.codes over streamable HTTP; OAuth sign-in to a moa account is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your moa workspace, so the assistant can read meeting transcripts, decisions, to-dos and wiki content, which may include confidential discussions and personal remarks. Review the granted scopes before connecting.

Installation

In SourceWeft

  1. Open moa in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/codes.moa%2Fmoa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "moa": {
      "type": "http",
      "url": "https://mcp.moa.codes/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 18, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.