Hearth
rsvp.hearthPublished by hearth.rsvpOfficial publisherv1.1.0Updated Oct 24, 2026
Plan gatherings with Hearth invitations: draft events, add guests, check RSVPs. Host confirms.
Overview
Lets an assistant draft events, add guests, and check RSVPs for gatherings planned through Hearth invitations.
- What you can do
- Hearth is a remote MCP server for planning gatherings with Hearth invitations. According to its description, it lets an assistant draft events, add guests, and check RSVPs. The description also notes that the host confirms, so the assistant's role appears to be preparing invitation details rather than finalizing them. No individual tools are listed in the manifest.
- When to use it
- Use it when you organize gatherings through Hearth and want an assistant to prepare event drafts, build guest lists, and look up RSVP status while you coordinate. It is less useful if you do not use Hearth invitations or need tools beyond event and guest planning. The description indicates the host still confirms, so it fits a drafting and checking role rather than fully automated sending.
- Requirements
- A remote MCP endpoint at using streamable HTTP. OAuth authentication is required. No packages, environment variables, or headers are declared.
Installation
In SourceWeft
- Open Hearth 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/rsvp.hearth%2Fhearth/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": {
"hearth": {
"type": "http",
"url": "https://hearth.rsvp/api/mcp"
}
}
}Tools
0Version history
1- v1.1.0LatestSep 27, 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.
