Kokkai Minutes MCP Agent

Created By
egegungordua year ago
A Model Context Protocol (MCP) agent for accessing the Japanese National Diet Library's Kokkai Minutes API | 国会議事録APIにアクセスするためのMCPエージェント
Overview

What is Kokkai Minutes MCP Agent?

Kokkai Minutes MCP Agent is a Model Context Protocol (MCP) agent designed to provide a structured interface for accessing the Japanese National Diet Library's Kokkai Minutes API, which contains parliamentary proceedings.

How to use Kokkai Minutes MCP Agent?

To use the Kokkai Minutes MCP Agent, you can access the live deployment at https://kokkaikaigiroku-mcp.egeg.workers.dev/mcp and utilize its API functions to search for parliamentary meetings and speeches.

Key features of Kokkai Minutes MCP Agent?

  • Provides a standardized interface for accessing parliamentary proceedings.
  • Supports searching for meetings and speeches with various parameters.
  • Allows AI models to retrieve and analyze political discussions and historical debates.

Use cases of Kokkai Minutes MCP Agent?

  1. Conducting policy research by querying discussions on specific topics.
  2. Performing political analysis by comparing party positions on issues.
  3. Engaging in historical research by finding debates from specific time periods.

FAQ from Kokkai Minutes MCP Agent?

  • Can I access all parliamentary proceedings?

Yes! The agent allows you to search and retrieve a wide range of parliamentary proceedings.

  • Is there a cost to use the Kokkai Minutes MCP Agent?

No! The agent is free to use for everyone.

  • What programming languages are supported?

The agent is built using TypeScript and runs on Cloudflare Workers.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
egegungordu
Star
0
Language
TypeScript
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)

a day ago