European-Parliament

The European Parliament MCP Server provides a TypeScript/Node.js implementation of the Model Context Protocol (MCP) tailored to European Parliament Open Data. It exposes structured access to a range of EP datasets, including information about MEPs, plenary sessions, committees, legislative documents, parliamentary questions, and OSINT capabilities such as influence scoring, coalition analysis, and anomaly detection. The server is designed for AI assistants, IDEs, and MCP clients to query EP data with type safety and fast responses. You can leverage the 61 tools (core, advanced, OSINT, Phase 4/5, and feeds) to build rich conversational or analytical workflows that reason over parliamentary information, track legislative activity, and perform cross-cut analyses while respecting security and provenance requirements.

Prerequisites:

• Node.js (LTS) and npm installed on your system
• git (optional but recommended for cloning)

Installation steps:

1. Install the MCP server package from npm (global or local project):
   • Global install (optional): npm install -g european-parliament-mcp-server
   • Local project usage: mkdir -p my-project && cd my-project && npm init -y && npm install european-parliament-mcp-server
2. If you prefer running directly with npx (no local install):
   • npx -y european-parliament-mcp-server
3. Start the server in your environment:
   • If installed locally: npx -y european-parliament-mcp-server
   • If installed globally: european-parliament-mcp-server
4. (Optional) Configure environment variables and runtime options as needed for your deployment (see additional_notes below for common vars).

Notes and tips:

• This MCP server is built with TypeScript in strict mode and uses Zod for runtime validation to ensure data integrity when querying EP Open Data.
• Typical environment variables you may want to configure include API keys, access controls, caching settings, and logging levels. Example placeholders: API_BASE_URL, EP_API_KEY, LOG_LEVEL, CACHE_TTL.
• If you deploy behind a reverse proxy or in a container, ensure proper CORS settings if you expose the MCP API to web clients.
• The server provides OSINT capabilities (e.g., influence scoring, coalition analysis). Validate any sensitive data handling against your compliance requirements.
• For production, enable provenance and provenance-related checks (SLSA level 3 or higher is recommended) and monitor test coverage to maintain reliability.