time-mcp

Created By
suryawanshishantanu6a year ago
MCP Server which returns current timestamp with streamlit app
Overview

what is time-mcp?

Time-mcp is a minimal agentic AI system designed to answer time-related and general questions using a tool-augmented LLM pipeline. It provides the current timestamp through a Flask API and features a Streamlit UI for user interaction.

how to use time-mcp?

To use time-mcp, clone the repository, install the dependencies, set your OpenRouter API key, and run the Flask API, MCP Agent Server, and Streamlit UI in separate terminals. You can then interact with the AI agent through the Streamlit interface.

key features of time-mcp?

  • Flask API for providing the current timestamp.
  • MCP Agent Server for detecting user intent and interacting with an LLM.
  • Streamlit UI for a simple chat interface with the AI agent.

use cases of time-mcp?

  1. Answering questions about the current time.
  2. Providing general information through natural language responses.
  3. Extending functionality by adding more tools to the MCP Agent.

FAQ from time-mcp?

  • Can time-mcp answer any question?

Yes, it can answer time-related questions and general inquiries using the LLM.

  • How do I set up time-mcp?

Follow the setup instructions in the documentation to clone the repo, install dependencies, and run the servers.

  • Is time-mcp customizable?

Yes, you can add more tools and improve intent detection by modifying the MCPAgent class.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
suryawanshishantanu6
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