EpicMe MCP is an application that demonstrates the Model Context Protocol (MCP), allowing users to interact with it via natural language through LLMs.

What is MCP (Model Context Protocol)?

MCP is an open protocol that standardizes how applications provide context to Large Language Models (LLMs), enabling them to access and interact with external data sources and tools.

How does EpicMe MCP handle authentication?

It uses a unique flow where a grant is automatically generated for new users, who then claim it via a TOTP code sent to their email.

What are the benefits of using UBOS with EpicMe MCP?

UBOS provides tools for AI Agent orchestration, enterprise data connectivity, custom AI Agent development, Multi-Agent Systems, and ensures scalability and reliability.

What is the known issue with EpicMe MCP, and how can UBOS help?

The known issue involves client registration inconsistencies when the `.wrangler` directory is deleted. UBOS can resolve this with a robust client management system, centralized client registry, and automated re-registration processes.

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.

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.