DoorstopMCP
A MCP Server for the Doorstop Requirements Engineering Framework
claude mcp add --transport stdio jannled-doorstopmcp docker compose up --force-recreate
How to use
DoorstopMCP provides an MCP (Model Context Protocol) server wrapper around the Doorstop framework so you can interact with your Doorstop documents through MCP clients and tools. The server runs inside Docker and exposes multiple ports for different purposes: port 3001 serves the main DoorstopMCP server, port 7867 hosts a tweaked doorstop-server UI that updates on page reload, and ports 6274, 6277, and 3002 are used by MCP Explorer when starting Docker with the inspector profile. To get started, run the project with Docker Compose as described in the Quickstart. Once running, you can connect MCP clients to http://{HOST}:3001/mcp or inspect results via http://{HOST}:7867. You can also launch the MCP Explorer tool with the inspector profile to browse the MCP from a UI, or use the Inspector CLI (npx @modelcontextprotocol/inspector) to interact with the server from the command line. Note that this tool is not production-ready yet and has no user authentication, so only run it in a trusted network.
Usage flows include: connecting to the MCP via Streamable HTTP, sending item/document operations through the Doorstop integration, and using the provided UI to inspect results and export data. The README describes how to configure external tools like Open WebUI and Vibe CLI to point at http://YOUR_URL:3001/mcp, enabling a seamless workflow between your Doorstop data and MCP clients.
How to install
Prerequisites:
- Docker and Docker Compose installed on your system
- Git to clone the repository
Step-by-step:
-
Clone the repository: git clone <repository-url> cd <repo-directory>
-
Ensure Docker is running and that your environment has access to Docker Compose:
- On Linux/macOS: docker and docker-compose come bundled with Docker Desktop or Docker Engine
- On Windows: use Docker Desktop
-
Start the MCP server via Docker Compose: docker compose up --force-recreate
-
Verify the services are up by checking the logs or visiting the UI:
- Main MCP server: http://localhost:3001/mcp
- Inspector UI: http://localhost:7867
-
(Optional) If you modify the docker-compose setup, you can rebuild containers: docker compose down docker compose up --force-recreate --build
Additional notes
Notes and tips:
- This MCP server is intended for development and testing. There is no user authentication yet; use in trusted networks only.
- The Inspector profile for MCP Explorer runs under ports 6274, 6277, and 3002 when using Docker with the inspector profile enabled.
- If you customize the Doorstop configuration, ensure that the MCP server URL remains stable for your clients (e.g., http://localhost:3001/mcp).
- Open WebUI and Vibe CLI configurations are provided in the README to help you connect external tools to this MCP server.
- If you encounter port conflicts, adjust your docker-compose file or map to different host ports as needed.
Related MCP Servers
nautex
MCP server for guiding Coding Agents via end-to-end requirements to implementation plan pipeline
mcp-yfinance
Real-time stock API with Python, MCP server example, yfinance stock analysis dashboard
pfsense
pfSense MCP Server enables security administrators to manage their pfSense firewalls using natural language through AI assistants like Claude Desktop. Simply ask "Show me blocked IPs" or "Run a PCI compliance check" instead of navigating complex interfaces. Supports REST/XML-RPC/SSH connections, and includes built-in complian
cloudwatch-logs
MCP server from serkanh/cloudwatch-logs-mcp
servicenow-api
ServiceNow MCP Server and API Wrapper
the -company
TheMCPCompany: Creating General-purpose Agents with Task-specific Tools