Infobús MCP

Created By
simovilaba year ago
MCP server to interact with the Infobús transit API
Overview

what is Infobús MCP?

Infobús MCP is a server designed to interact with the Infobús transit API, providing a way to access and manage transit data effectively.

how to use Infobús MCP?

To use Infobús MCP, set up the server and connect it to the Infobús transit API. You can then make API calls to retrieve transit information.

key features of Infobús MCP?

  • Seamless integration with the Infobús transit API
  • Ability to manage and retrieve transit data
  • Built using Python for easy customization

use cases of Infobús MCP?

  1. Accessing real-time transit information for users.
  2. Integrating transit data into applications for better user experience.
  3. Analyzing transit patterns and data for research purposes.

FAQ from Infobús MCP?

  • What programming language is Infobús MCP built with?

Infobús MCP is built using Python.

  • Is there any documentation available?

Yes, you can find the documentation on the GitHub repository.

  • Can I contribute to the project?

Yes, contributions are welcome! Please check the contribution guidelines on the GitHub page.

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