Dominican Congress MCP Server

Created By
EnzoVezzaroa year ago
This MCP server provides access to information about the Dominican Congress, including legislative agendas, legislator activity, and new bills.
Overview

What is the Dominican Congress MCP Server?

The Dominican Congress MCP Server provides access to information about the Dominican Congress, including legislative agendas, legislator activity, and new bills.

How to use the Dominican Congress MCP Server?

To use the server, clone the repository from GitHub, install the dependencies, and configure your MCP client to recognize the server. You can then use various tools to fetch legislative information.

Key features of the Dominican Congress MCP Server?

  • Fetch legislative agendas for different chambers.
  • Retrieve activity for specific legislators.
  • Summarize today's legislative activity.
  • Access new bills for legislative chambers.
  • Parse PDF, CSV, and XLSX files from URLs.

Use cases of the Dominican Congress MCP Server?

  1. Accessing real-time legislative agendas for the Dominican Congress.
  2. Monitoring the activity of specific legislators.
  3. Summarizing legislative activities for reports.
  4. Fetching and parsing legislative documents in various formats.

FAQ from the Dominican Congress MCP Server?

  • What types of data can I access?

You can access legislative agendas, legislator activities, and new bills.

  • How do I configure the MCP client?

Follow the installation instructions to add the server configuration to your MCP client's settings.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
EnzoVezzaro
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago