Skip to content

Add Promptise Foundry to Frameworks (servers + clients) - #4038

Closed
cryxnet wants to merge 4 commits into
modelcontextprotocol:mainfrom
cryxnet:add-promptise-foundry
Closed

Add Promptise Foundry to Frameworks (servers + clients)#4038
cryxnet wants to merge 4 commits into
modelcontextprotocol:mainfrom
cryxnet:add-promptise-foundry

Conversation

@cryxnet

@cryxnet cryxnet commented Apr 24, 2026

Copy link
Copy Markdown

Adds Promptise Foundry (Python, Apache 2.0) as a high-level framework that covers both sides of MCP — so it belongs in both the ### For servers and ### For clients lists under ## 📚 Frameworks.

Promptise Foundry is the MCP framework for building secure, scalable MCP servers with real access control and a FastAPI-style developer experience. On the server side: JWT / RS256 / ES256 / API-key authentication, capability-based guards, a composable middleware chain (rate limiting, circuit breakers, caching, HMAC-chained audit, Prometheus, OpenTelemetry), dependency injection via Depends(), per-tool versioning, streaming, elicitation, sampling, and an in-process TestClient. On the client side: a native MCP implementation (no third-party MCP client deps) over stdio / SSE / streamable HTTP with bearer and API-key auth, automatic tool discovery, and unified routing across multiple servers.

Placed alphabetically within each list and formatted to match neighboring entries (FastMCP, ModelFetch, Quarkus MCP Server SDK, Spring AI MCP Client). CONTRIBUTING.md's rule against new server implementations does not apply — this is a framework listing, not a server.

@cryxnet

cryxnet commented Jun 4, 2026

Copy link
Copy Markdown
Author

bump

@LuuOW LuuOW left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technical audit: Verified MCP server implementation for consistency with current SDK patterns.

@cryxnet

cryxnet commented Jun 19, 2026

Copy link
Copy Markdown
Author

Hi @LuuOW ,
I see there are some bigger changes within the README, seems like the list of 3party MCP frameworks are now in ADDITIONAL.md. Should I adapt?

@cryxnet

cryxnet commented Jun 28, 2026

Copy link
Copy Markdown
Author

Hi, any updates?

@localden

Copy link
Copy Markdown
Contributor

Thanks for the submission. We no longer accept server, resource, or tooling submissions to this repository; it is dedicated to the small set of reference servers maintained by the MCP steering group. To make your project discoverable, please publish it to the MCP Registry: https://registry.modelcontextprotocol.io/

@localden localden closed this Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants