Model Context Protocol (MCP) Server for Graphlit Platform

Created By
graphlita year ago
Model Context Protocol (MCP) Server for Graphlit Platform
Overview

What is Graphlit MCP Server?

The Graphlit MCP Server is a Model Context Protocol (MCP) Server designed for the Graphlit Platform, enabling seamless integration between MCP clients and the Graphlit service for data ingestion and retrieval.

How to use Graphlit MCP Server?

To use the Graphlit MCP Server, install it via npm or Smithery, configure your environment variables for authentication, and connect it to various data sources like Slack, Gmail, and more.

Key features of Graphlit MCP Server?

  • Ingest data from multiple sources including documents, emails, and web pages.
  • Extract content into structured formats like Markdown and JSON.
  • Support for audio and video transcription upon ingestion.
  • Integration with various data connectors and APIs.

Use cases of Graphlit MCP Server?

  1. Collecting and processing data from emails and chat applications.
  2. Extracting content from web pages for analysis.
  3. Transcribing audio and video files for content creation.

FAQ from Graphlit MCP Server?

  • What types of data can be ingested?

The server can ingest documents (PDF, DOCX, PPTX), HTML web pages, audio, and video files.

  • Is there a cost associated with using the Graphlit MCP Server?

The server is free to use, but may require an account on the Graphlit Platform for full functionality.

  • How do I configure the server?

Configuration is done through environment variables for authentication and data source connections.

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

20 hours ago
Gpt Scrambler

2 days ago