Metis MCP Tools

Created By
dagron78a year ago
A demo repository for testing the GitHub MCP server
Overview

What is Metis MCP Tools?

Metis MCP Tools is a demo repository that provides a collection of Model Context Protocol (MCP) tools designed to enhance the Metis RAG application, enabling interaction with databases, vector stores, document processing, and language model interactions.

How to use Metis MCP Tools?

To use Metis MCP Tools, clone the repository, install the dependencies, and start the desired MCP server. Then, connect to the MCP server from your application using an MCP client.

Key features of Metis MCP Tools?

  • Database Management Tool for PostgreSQL interactions
  • Vector Store Tool for managing vector databases
  • Document Processing Tool for loading and processing documents
  • LLM Interaction Tool for generating text with language models

Use cases of Metis MCP Tools?

  1. Managing and querying PostgreSQL databases in Metis applications.
  2. Interacting with vector databases for similarity searches.
  3. Processing various document formats for analysis.
  4. Generating text and embeddings using language models.

FAQ from Metis MCP Tools?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized way for language models to interact with external tools and resources.

  • How do I install Metis MCP Tools?

Clone the repository, install dependencies, and start the MCP servers as described in the documentation.

  • Can I contribute to Metis MCP Tools?

Yes! Contributions are welcome through pull requests or issue submissions.

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