prospectio-api
MCP/API server that helps you to connect to different lead generation app
claude mcp add --transport stdio prospectio-ai-prospectio-api-mcp python -m prospectio_api_mcp.main \ --env ENV_FILE=".env path or variable" \ --env LOG_LEVEL="INFO|DEBUG|WARNING (optional)" \ --env DATABASE_URL="PostgreSQL connection string (e.g., postgres://USER:PASS@HOST:PORT/DB)" \ --env DATABASE_HOST="database host (alternative to DATABASE_URL)" \ --env DATABASE_NAME="database name (alternative to DATABASE_URL)" \ --env DATABASE_PORT="database port (alternative to DATABASE_URL)" \ --env DATABASE_USER="database user (alternative to DATABASE_URL)" \ --env DATABASE_PASSWORD="database password (alternative to DATABASE_URL)"
How to use
This MCP server exposes two primary interfaces. First, a REST API under /rest/v1/ for standard CRUD and report operations related to leads and profiles. Second, the MCP protocol endpoint under /prospectio/ enables Model Context Protocol interactions for programmatic lead prospecting, where MCP clients can request lead data, profiles, and related context. The application is built with FastAPI and follows Clean Architecture, separating domain, application, and infrastructure concerns. To begin, ensure your environment is configured (see installation steps) and start the server; you will be able to insert and retrieve leads via use cases, as well as manage profiles. The server integrates with PostgreSQL for persistent storage and supports vector-enabled data through pgvector for efficient similarity and matching operations. When running, consider using a client that speaks MCP to fetch leads, insert results, or query profiles as part of a multi-source prospecting workflow.
How to install
Prerequisites:
- Python 3.11+ installed on your machine or server
- PostgreSQL database available and reachable
- git installed to clone the repository
- Clone the repository
- git clone https://github.com/your-org/prospectio-api-mcp.git
- cd prospectio-api-mcp
- Create and configure a virtual environment
- python -m venv venv
- source venv/bin/activate # On Windows: venv\Scripts\activate
- Install Python dependencies
- pip install -U pip setuptools wheel
- pip install -r pyproject.toml # If using Poetry, install via Poetry as below
- Install via Poetry (recommended for this project)
- curl -sSL https://install.python-poetry.org | python3 -
- poetry install
- Configure environment
- Copy example env and tailor database settings
- cp .env.example .env
- edit .env to include DATABASE_URL or components (host, port, user, password, dbname)
- Prepare the database
- (Optional) Run any provided initialization scripts
- Create PostgreSQL database and enable pgvector extension if needed
- Run the server
- poetry run python -m prospectio_api_mcp.main
- Or if not using Poetry: python -m prospectio_api_mcp.main
- Verify the server
- Access REST API at http://localhost:8000/rest/v1/
- Access MCP endpoint at http://localhost:8000/prospectio/
Additional notes
Tips and common considerations:
- Ensure the .env or environment variables provide a valid PostgreSQL connection string (DATABASE_URL) or individual components (DATABASE_HOST, DATABASE_PORT, etc.).
- The server uses FastAPI with a Clean Architecture layout; dependencies are injected per endpoint, making it straightforward to swap data sources or storage implementations via the Ports/Adapters pattern.
- If you enable advanced features, you may want to preload leads or profiles during startup for faster MCP responses.
- For production, consider running behind a reverse proxy (e.g., Nginx) and enabling TLS. Monitor logs with the LOG_LEVEL setting and consider configuring a proper WSGI/ASGI server stack (e.g., uvicorn with Gunicorn) for production deployments.
- When debugging, check the PostgreSQL schema in database/init.sql and ensure the required tables exist before inserting leads.
Related MCP Servers
fastapi_mcp
Expose your FastAPI endpoints as Model Context Protocol (MCP) tools, with Auth!
sec-edgar
A SEC EDGAR MCP (Model Context Protocol) Server
MCP-PostgreSQL-Ops
🔍Professional MCP server for PostgreSQL operations & monitoring: 30+ extension-independent tools for performance analysis, table bloat detection, autovacuum monitoring, schema introspection, and database management. Supports PostgreSQL 12-17.
dremio
Dremio MCP server
ContextPods
Model Context Protocol management suite/factory. An MCP that can generate and manage other local MCPs in multiple languages. Uses the official SDKs for code gen.
okta
The Okta MCP Server is a groundbreaking tool built by the team at Fctr that enables AI models to interact directly with your Okta environment using the Model Context Protocol (MCP). Built specifically for IAM engineers, security teams, and Okta administrators, it implements the MCP specification to help work with Okta enitities