🚀 API Revolution: Model Context Protocol (MCP) Meets Web API
LocalAbout 🚀 API Revolution: Model Context Protocol (MCP) Meets Web API
An ASP.NET Core Web API that routes registration, login, and password-change prompts through an MCP client to an MCP server. It keeps bearer tokens from API users and separates business logic into domain-oriented layers.
Key features
- 01Email-based user registration
- 02Login and password changes
- 03ASP.NET Core API endpoints
- 04Domain-driven layered architecture
- 05Structured logging and error handling
Use cases
- 01Register an account by submitting an email prompt
- 02Log in and request a password change through an API
- 03Add tools to extend the API workflow
MCP support
The API forwards requests through an MCP client to an MCP server and returns the response to the caller. It is an MCP-facing backend rather than a server exposing tools directly.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README🚀 API Revolution: Model Context Protocol (MCP) Meets Web API
Welcome to MCP Server Tools! 🎯
This project exposes powerful APIs based on the Model Context Protocol (MCP) 🧩, representing a new revolution in API design 🌐 — structured, intelligent, and seamlessly extensible.
📚 Overview
- 🛠️ Combines Model Context Protocol (MCP) with traditional API endpoints to offer next-generation API experiences.
- 🔥 Redefines API architecture by enabling model-based communication, not just rigid HTTP contracts.
- 🧠 Applies Domain-Driven Design (DDD) at the core: aggregates, entities, and use cases are clearly separated and modeled around business logic.
- 🔐 Secures workflows like registration, login, and password change using industry best practices.
- 🧪 Extensible and modular — new tools can be added easily without modifying the core.
- 📈 Built with professional engineering principles: structured logging (via Serilog), robust error handling, clean separation of concerns.
🧩 Architecture Flow
Client ➡️ API Endpoint (ASP.NET Core) ➡️ MCP Client ➡️ MCP Server ➡️ Response
✅ You send a request to our API,
✅ We internally call the MCP Client,
✅ MCP Client talks to MCP Server,
✅ We return the clean final response to the API caller.
In short: You just send simple prompts, we handle everything behind the scenes. 🎩✨
🔥 Example Usage
📬 Register a New User
POST to:
https://localhost:7190/api/Prompt/SendUserPrompt/SendUserPrompt
Request body:
{ "Prompt": "hei dawg! my email: [email protected] please help me to register" }
Response:
Great! An email with your login details should be on its way.
Check your inbox for an email from us, containing your email address and password.
Remember to change your password after your first login for added security.
If you don't receive the email, please let me know and we'll try again.
🔒 Login and Change Password
POST to:
https://localhost:7190/api/Prompt/SendUserPrompt/SendUserPrompt
Request body:
{ "Prompt": "Bro Server! now please login me email: [email protected] and password: d8X9sF & change the password with 123456" }
Response:
Sure, I'll help you with that.
Now that you're logged in, I'll help you change your password to '123456'.
Your password has been successfully changed. If you have any other requests, feel free to let me know!
🛠️ Tech Stack
- 🧩 Model Context Protocol (MCP)
- ⚡ ASP.NET Core Web API
- 🧠 Domain-Driven Design (DDD) Architecture
- 🛡️ Serilog for structured logging
- 🛠️ Clean architecture principles
- ✨ Professional software practices
📌 Key Highlights
- 🚫 We never expose sensitive Bearer tokens to users.
- 🧠 Designed using DDD-first thinking: domain-driven layers and bounded contexts.
- 🌱 Future-proof and easily extendable.
- 🧹 Clean separation between API, application, and domain logic.
📜 License - Apache License 2.0 (TL;DR)
This project follows the Apache License 2.0, which means:
- ✅ You can use, modify, and distribute the code freely.
- ✅ You must include the original license when distributing.
- ✅ You must include the
NOTICEfile if one is provided. - ✅ You can use this in personal & commercial projects.
- ✅ No warranties – use at your own risk! 🚀
🚀 Join the API Revolution!
APIs should be smart, dynamic, and model-based — not static and hardcoded.
Be part of the change! 🌟
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.