EphemeralMe Protocol Conduit

This service instance serves as a prototypical demonstration, operating solely through the Model Context Protocol (MCP) interface.

All operational facets, spanning from securing user credentials to transactional data access, are mediated exclusively through defined MCP functions.

The primary objective is to illustrate a prospective paradigm for application interaction: users engaging with sophisticated software purely through natural language dialogue mediated by LLMs leveraging the MCP specification. This forms the foundational instruction set for developing MCP utilities on EpicAI.pro.

Operational Guide

⚠️ Critical Warning: This environment is strictly for experimental evaluation; it is not a production deployment. Service level agreements (SLAs), data confidentiality assurances, or established data lifecycle policies are explicitly absent. Usage is undertaken entirely at the user's own peril; refrain from submitting any sensitive or critical information.

Service Endpoint

The EphemeralMe MCP engine is reachable at the following network location:

https://epic-me-mcp.kentcdodds.workers.dev/mcp

Functional Capabilities

EphemeralMe functions as a private digital chronicle system, supporting the following capabilities:

• Archival Management: Creation and modification of personal log entries, incorporating metadata such as thematic titles, narrative body, emotional state logging, geographical context, atmospheric readings, and access restriction levels.
• Categorization: Applying organizational markers (tags) to entries for enhanced retrieval and grouping.
• Intelligence Augmentation: Receiving LLM-derived tag recommendations for new entries.
• Synthesis: Generating consolidated summaries of recorded entries, with optional filters based on predefined tags or temporal spans.
• Preference Setting: Designating entries as favored items and establishing granular access permissions.

Initialization Sequence

1. Connection Establishment: Link to the designated MCP gateway using a compatible MCP client framework (e.g., Claude Desktop).
2. Identity Affirmation: Initiate authentication by submitting a valid electronic mail address; a one-time verification token will be dispatched to that address.
3. Engagement Commencement: Commence interaction with the journaling features using descriptive natural language instructions.

Credentialing Procedure

The initiation of user access possesses a distinctive characteristic, designed to onboard previously unrecognized user accounts:

1. Invoke the authenticate utility, supplying the designated electronic mail identifier.
2. Monitor the inbox associated with that address for the received Time-based One-Time Password (TOTP) validation sequence.
3. Complete the session linkage by invoking the validate_token utility with the received code.
4. Full access to all secured operational capabilities is then granted.

Exposed Utilities

Initial Access Utilities (Pre-Authorization)

• authenticate: Triggers the credential initiation routine using an email address.
• validate_token: Finalizes the access grant via the email-transmitted verification code.

User State Utilities (Post-Authorization)

• whoami: Fetches contextual metadata pertaining to the presently active identity.
• logout: Revokes the current authentication session.

Chronicle Record Utilities (Post-Authorization)

• create_entry: Generates a novel chronicle entry, optionally furnishing initial metadata like categorization labels, sentiment markers, location stamps, and environmental conditions.
• get_entry: Retrieves the specific content associated with a unique entry identifier.
• list_entries: Queries and returns a manifest of stored entries, supporting filtering based on specified categorization labels.
• update_entry: Modifies any attribute associated with an extant record.
• delete_entry: Permanently erases a specified chronicle entry.

Label Management Utilities (Post-Authorization)

• create_tag: Establishes a novel organizational label for entry association.
• get_tag: Retrieves the definition details for an identified label.
• list_tags: Presents a directory of all managed organizational labels.
• update_tag: Alters the attributes of an existing label.
• delete_tag: Removes an organizational label.
• add_tag_to_entry: Creates a directional link between a label and a specific record.

Available Conversational Directives

• suggest_tags: Provides AI-generated recommendations for applicable organizational labels for a given chronicle entry.
• summarize_journal_entries: Produces a distilled overview of stored entries, optionally constrained by label sets or a specified temporal window.

Accessible Information Endpoints (Resources)

• epicme://credits: Information regarding service resource allocation and attribution.
• epicme://users/current: Current user profile data.
• epicme://entries/{id}: Raw data payload for a singular chronicle entry.
• epicme://entries: Indexed collection manifest of all personal entries.
• epicme://tags/{id}: Detailed specification for an individual organizational label.
• epicme://tags: Comprehensive registry of all established organizational labels.

Illustrative Command Examples

Users can issue commands such as:

• "Initiate session establishment using my primary email address."
• "Compose a fresh log entry detailing my recent seaside excursion."
• "Generate a complete listing of all my stored records."
• "Display only those entries categorized under the 'professional duties' marker."
• "Propose suitable labels for my most recent documentation."
• "Provide a digest of my records logged within the preceding seven days."
• "Modify the status of that entry to designate it as a saved favorite."
• "Define a new organizational marker named 'long-term objectives'."

Access Grant Mechanism

The authentication pathway is engineered specifically to accommodate initial user setup where no prior credential set exists (requiring registration). Consequently, an access grant is algorithmically secured without necessitating the user to manually undergo an OAuth procedure. The user then validates this generated grant using the pre-emailed verification code.

This methodology proves sufficiently robust for the intended purpose.

Operational Caveats

During development phases, the purging of the .wrangler directory results in the elimination of dynamically provisioned client session data. These orphaned clients lack awareness of subsequent record deletions and will not autonomously attempt re-registration. Within the MCP Inspector interface, clearing the browser's session storage is the method to force re-instantiation of client registration. Equivalent mechanisms for external client frameworks remain undetermined by the developer.