hasmcp/hasmcp-ce

HasMCP is a tool that converts API endpoints into MCP Server without writing a single line of code. It is practical alternative for developers and SaaS owners who prefers not to develop anad maintain MCP spec changes over time.
HasMCP-CE shares the some logic for the commercial
versions of the HasMCP-Pro and HasMCP-Enterprise.
NOTE: HasMCP-Pro and HasMCP-Enterprise versions are maintained in private repositories and source codes are not available. HasMCP Cloud service itself uses the HasMCP-Enterprise edition on
production.
## HasMCP-CE Features
Automated MCP server creation using OpenAPI Spec v3+ and Swagger
Oauth2 authentication
Manual MCP from API endpoints
Toggle endpoints per MCP Server
Proxy headers (optional per MCP Server) to actual API endpoints
Long term, short-term authentication tokens per MCP Server
Real-time MCP Server method/tool call logs
Real-time MCP server analytics (added in v0.2.2)
Optional automated SSL with Let's encrypt
## HasMCP Cloud Features
Cloud version is available with Hobby(with monthly free-tier) and Pro subscriptions at hasmcp.com. It has some additonal features compared to the Community Edition:
Request/response payload optimization per tool with a minimum coding (interceptors). Up to 98% token reduction on MCP tool responses (depending on what is needed by the described tool).
Per tool call, per user usage analytics
Users, teams management (Pro and Enterprise only)
Audit logs (Enterprise only)
Why does it have cloud version?
To support futher development
Help developers and companies those are not interested in running a server and maintain it
Entrepreneurship
## HasMCP-CE Demo
## Roadmap
### Highest priority
[ ] Bug fixes (Highest priority)
[ ] Protocol updates
### HasMCP-CE (including Pro and Enterprise) short term roadmap
Functionality and token optimizations
[ ] MCP composition with Search/Add/Remove by LLMs directly (ETA: January 2026)
[ ] Toon format on responses (ETA: January 2026)
Extended protocol support
[ ] GRPC support (ETA: February 2026)
### Long term road map
[ ] Github integration (Git as source of truth)
[ ] Your requirements
## Development
HasMCP-CE is using monorepo approach that hosts both frontend and backend codes in the same
repository.
### Directory Structure
hasmcp-ce
|- backend # backend for hasmcp-ce
|- frontend # front-end for hasmcp-ce
|- COMMERCIALLICENSE # Commercial license
|- Dockerfile # Dockerfile
|- LICENSE # License file
|- Makefile # Handy Make commands to help developers
|- README.md # The current file that you are reading now
Development environment requires 2 services up and running at the same time:
1. Frontend
cd frontend
npm run dev # this will open port 5173
2. Backend
cd backend/cmd/server
go run main.go
3. Database
By default hasmcp-ce uses sqlite so you don't need to do anything. It is more than enough for single user experience.
To enable Postgres instead of Sqlite, you can add the following to the your .env file
POSTGRESENABLED=false # set true to use postgres as production db
# below are the your db connection details for postgres
POSTGRESTIMEZONE=UTC
POSTGRESUSER=postgres
POSTGRESPASSWORD=postgres
POSTGRESHOST=localhost
POSTGRESPORT=5432
POSTGRESDBNAME=postgres