The EpicMe MCP server is an experimental personal journaling application and MCP tool demonstration platform that provides:
Journaling Features: Create, manage, and organize journal entries with tags, moods, and privacy settings. Get AI-powered tag suggestions and summaries.
User Management: Authenticate users via email with TOTP validation, manage authentication sessions, and access user information.
Tag Management: Create, update, delete, and associate tags with journal entries.
MCP Demonstrations: Echo messages, add numbers, simulate long-running operations with progress updates, demonstrate message annotations (error, success, debug), provide resource references (ID 1-100), and showcase user elicitation for gathering information like favorite color, number, and pets.
Utilities: Print environment variables for debugging, sample text from LLMs, fetch tiny image references, return multiple resource links, and provide structured content like weather data with schema validation.
EpicMe MCP
This is an example of an application that's exclusively accessible via Model Context Protocol (MCP).
Everything from user registration and authentication to interacting with user data is handled via MCP tools.
The goal is to demonstrate a possible future of applications where users interact with our apps via natural language with LLMs and the MCP protocol. This will also be the basis upon which I will teach how to build MCP tools on EpicAI.pro.
Authentication
The authentication flow is unique because we need to be able to go through OAuth for users who don't exist yet (users need to register first). So we generate a grant automatically without the user having to go through the OAuth flow themselves. Then we allow the user to claim the grant via a TOTP code which is emailed to them.
This works well enough.
Related MCP server: MCP Base
Known Issues
During development, if you delete the .wrangler directory, you're deleting the
dynamically registered clients. Those clients don't know that their entries have
been deleted so they won't attempt to re-register. In the MCP Inspector, you can
go in the browser dev tools and clear the session storage and it will
re-register. In other clients I do not know how to make them re-register.