What authentication method does the server use?
The server uses API key authentication. Each user is assigned a unique `apiKey`, which clients provide as a query parameter (e.g., `/sse?apiKey=...`) to authenticate.
@scitara-cto
Basic information
A flexible and extensible framework for building Model Context Protocol (MCP) servers that conforms to the [Model Context Protocol specification](
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Dynamic MCP Server Framework is a flexible, extensible framework for building Model Context Protocol (MCP) servers. It supports API key–based authentication, MongoDB-backed user management and authorization, session-based per-user tool loading, and dynamic tool sharing with fine-grained access control.
Install via npm or clone the repository, then follow the Getting Started guide. Tools are registered as handler packages; the server is configured programmatically. Clients authenticate by passing the user’s apiKey as a query parameter (e.g., /sse?apiKey=...).
The server uses API key authentication. Each user is assigned a unique `apiKey`, which clients provide as a query parameter (e.g., `/sse?apiKey=...`) to authenticate.
Tools are registered via handler packages. Each package groups related tools and provides a handler function for execution. Tools can be created, deleted, and authorized at runtime—not limited to static startup definitions.
Yes. The framework supports tool sharing with fine-grained access control. Users can share tools with others and manage access levels through provided API actions.
Yes. The framework allows adding custom HTTP routes and MongoDB collections, enabling downstream projects to extend the server’s functionality.
All tools are visible to users by default. Users can hide tools from their view using the `hide-tool` and `unhide-tool` actions.
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools
MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.

Turn Perfex CRM into an AI-ready workspace. This MCP server exposes your full REST API to Claude, ChatGPT and any AI agent, so leads, invoices and tasks are one prompt away.
Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.
Comments