MoNomo: Ex-Mormon and Post-Mormon Meetups, Resources and Podcasts
com.monomoappPublished by monomoapp.comOfficial publisherv1.0.1Updated Oct 30, 2026
Ex-Mormon meetups and resources. Not affiliated with The Church of Jesus Christ of Latter-day Saints
Overview
Remote MCP endpoint for ex-Mormon and post-Mormon meetups, resources and podcasts, not affiliated with the LDS Church.
- What you can do
- The listing gives no tool list, so capabilities are known only from the short description.
- It is presented as a source of ex-Mormon and post-Mormon meetups and resources.
- Podcasts are named in the server's title as part of its scope.
- It is explicitly described as not affiliated with The Church of Jesus Christ of Latter-day Saints.
- When to use it
- Worth considering when an assistant should point people toward ex-Mormon or post-Mormon community meetups, resources or podcasts, for example during conversations about leaving or having left the LDS Church.
- Requirements
- A remote MCP endpoint at the provider's API host, reached over streamable HTTP. OAuth authentication is required, so the user must sign in with a supported account. No environment variables or headers are declared.
Installation
In SourceWeft
- Open MoNomo: Ex-Mormon and Post-Mormon Meetups, Resources and Podcasts in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/com.monomoapp%2Fmonomo/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"monomo-ex-mormon-and-post-mormon-meetups": {
"type": "http",
"url": "https://api.monomoapp.com/mcp"
}
}
}Tools
0Version history
1- v1.0.1LatestOct 30, 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.