Graphlit MCP Server

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL

https://heyclau.de/entry/mcp/graphlit-mcp-server

Source URLs

https://raw.githubusercontent.com/graphlit/graphlit-mcp-server/main/README.md, https://github.com/graphlit/graphlit-mcp-server

Brand

Graphlit MCP Server

Brand domain

graphlit.com

Brand asset source

brandfetch

Safety notes

Graphlit MCP Server can ingest files, web pages, messages, posts, emails, issues, text, memory, feeds, crawls, and connected SaaS data into a Graphlit project., Tools can create or delete contents, feeds, collections, conversations, specifications, and workflows, and can configure project defaults when explicitly requested., Web crawling, web search, screenshots, podcast search, feed scheduling, publishing, and connector operations may contact third-party services and process external content., Generated audio and image publishing can call configured model/provider services and consume credits or quota., Require confirmation before ingesting private repositories, emails, drive files, Slack/Teams/Discord data, customer documents, large crawls, generated media, deletion operations, or project configuration changes.

Privacy notes

Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client., Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot., Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content., Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations., Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data.

Author

Graphlit

Submitted by

oktofeesh1

Claim status

unclaimed

Last verified

2026-06-06

• Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client.
• Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot.
• Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content.
• Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations.
• Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data.

• Active Graphlit platform account and project access.
• Graphlit organization ID, environment ID, and JWT secret from the Graphlit API settings dashboard.
• Node.js 18 or newer for the npm stdio server.
• Review of which files, URLs, feeds, SaaS connectors, memories, conversations, collections, and web crawls Claude may create or query.
• Understanding of Graphlit usage credits, LLM token usage, connector permissions, and any third-party service costs configured for the project.

Show that Graphlit MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

[![Listed on HeyClaude](https://heyclau.de/badge/mcp/graphlit-mcp-server.svg)](https://heyclau.de/entry/mcp/graphlit-mcp-server)

Graphlit MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field	Graphlit MCP Server MCP server for the Graphlit platform, enabling Claude to ingest, search, retrieve, organize, and operate on files, web pages, feeds, collections, conversations, memory, connectors, crawls, and RAG-ready project knowledge. Open dossier	Agentset MCP Server Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions. Open dossier	Cyanheads Obsidian MCP Server Apache-licensed TypeScript MCP server for Obsidian vaults with stdio and Streamable HTTP transports, Local REST API access, note search, section-aware edits, tag/frontmatter management, path policies, and read-only controls. Open dossier	Omnisearch MCP Server MCP server that unifies web search, AI answer, GitHub search, and web extraction providers including Tavily, Brave, Kagi, Exa, Linkup, Firecrawl, and GitHub behind four consolidated tools. Open dossier
Next steps	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing	Open dossierCopy installCopy configAPI JSONOpen LLMMCP feedOpen sourceNewsletterClaim listing
Trust	Review first	Review first	Review first	Review first
Review status	Not reviewed	Not reviewed	Not reviewed	Not reviewed
Package trust	Package not verified	Package not verified	Package not verified	Package not verified
Source provenance	Source-backed	Source-backed	Source-backed	Source-backed
Submitter	oktofeesh1	oktofeesh1	oktofeesh1	oktofeesh1
Install risk	Review first	Review first	Review first	Review first
Notes	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓	Safety ✓ Privacy ✓
Brand	Graphlit MCP Server	Agentset	—	—
Category	mcp	mcp	mcp	mcp
Source	Source-backed	Source-backed	Source-backed	Source-backed
Author	Graphlit	Agentset	cyanheads	Scott Spence
Added	2026-06-06	2026-06-06	2026-06-06	2026-06-06
Platforms	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Harness	Claude CodeCodexCursorClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop	Claude CodeClaude Desktop
Source repo	—	—	—	—
Safety notes	✓Graphlit MCP Server can ingest files, web pages, messages, posts, emails, issues, text, memory, feeds, crawls, and connected SaaS data into a Graphlit project. Tools can create or delete contents, feeds, collections, conversations, specifications, and workflows, and can configure project defaults when explicitly requested. Web crawling, web search, screenshots, podcast search, feed scheduling, publishing, and connector operations may contact third-party services and process external content. Generated audio and image publishing can call configured model/provider services and consume credits or quota. Require confirmation before ingesting private repositories, emails, drive files, Slack/Teams/Discord data, customer documents, large crawls, generated media, deletion operations, or project configuration changes.	✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace. The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance. Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent. API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager. Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.	✓Cyanheads Obsidian MCP can read, list, search, create, append, patch, replace, delete, tag, and edit frontmatter in the configured vault through the Local REST API plugin. The server defaults to full-vault access unless read paths, write paths, or read-only mode are configured. Set `OBSIDIAN_READ_ONLY=true` for research-only workflows, then narrow writes with `OBSIDIAN_WRITE_PATHS` before allowing note edits. Delete operations are permanent in the vault and should require human review even when the MCP host supports destructive-tool prompts. Command-palette tools are disabled unless `OBSIDIAN_ENABLE_COMMANDS=true`; command execution can trigger opaque or destructive Obsidian plugin behavior. Streamable HTTP deployments should use JWT or OAuth auth before being exposed beyond a trusted local machine.	✓Omnisearch MCP Server can query multiple third-party search, AI answer, GitHub search, extraction, scraping, crawling, summarization, and content-processing providers. Firecrawl crawl, scrape, map, extract, and action modes can interact with websites and may trigger robots.txt, TOS, rate-limit, or authentication concerns. GitHub search depends on the configured token scope and can reveal private code, repositories, users, or organization metadata when a broad token is used. Large result mode can write response content to files; review where those files are stored before using it with private or regulated data. Require confirmation before crawling sites, extracting private URLs, using authenticated providers on sensitive targets, or running broad GitHub searches against private organizations.
Privacy notes	✓Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client. Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot. Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content. Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations. Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data.	✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data. Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry. Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base. Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.	✓Vault notes, headings, block references, frontmatter, tags, file metadata, outgoing links, search queries, command names, plugin status, and edit history may be exposed to the MCP client and model provider. API keys, local plugin endpoints, HTTP auth settings, path allowlists, logs, OpenTelemetry traces, and Docker environment variables can reveal private vault structure or credentials. Tag listing is vault-wide in upstream behavior and can reveal tag names outside narrowed read paths. Notes may contain personal journals, client work, credentials, meeting notes, research plans, health data, or other sensitive knowledge-base content.	✓Provider API keys, GitHub tokens, search queries, URLs, extracted page content, crawled site maps, scraped text, summaries, AI answers, GitHub search results, and large-result files can be exposed to the MCP client. Search and extraction providers may log queries, URLs, source content, account identifiers, usage metadata, and generated responses according to their own policies. Web extraction can capture personal data, paywalled content, internal URLs, or proprietary documents if supplied by the user or available to an authenticated provider. GitHub search output may include repository names, code snippets, file paths, commit metadata, and organization details. Keep provider credentials in local MCP configuration only, and avoid sharing transcripts that contain private queries, URLs, source text, or tokens.
Prerequisites	Active Graphlit platform account and project access. Graphlit organization ID, environment ID, and JWT secret from the Graphlit API settings dashboard. Node.js 18 or newer for the npm stdio server. Review of which files, URLs, feeds, SaaS connectors, memories, conversations, collections, and web crawls Claude may create or query.	Agentset account or self-hosted Agentset deployment with a populated namespace. Agentset API key with access to the namespace Claude should query. Node.js 18.17 or newer for running the `@agentset/mcp` package. Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.	Node.js 24 or newer, or Bun 1.3.11 or newer. Obsidian vault with the Obsidian Local REST API community plugin enabled. Local REST API key stored in the MCP client environment. Stdio MCP client, or reviewed Streamable HTTP deployment with authentication.	Node.js 22 or newer for the published npm package. At least one provider API key for Tavily, Kagi, Brave Search, GitHub, Exa, Linkup, or Firecrawl. Optional `FIRECRAWL_BASE_URL` when using a self-hosted Firecrawl instance. Optional `OMNISEARCH_LARGE_RESULT_MODE` choice for file or inline handling of large results.
Install	npx -y graphlit-mcp-server Copy install	Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment. Copy install	npx -y obsidian-mcp-server@latest Copy install	npx mcp-omnisearch Copy install
Config	{ "mcpServers": { "graphlit": { "command": "npx", "args": [ "-y", "graphlit-mcp-server" ], "env": { "GRAPHLIT_ORGANIZATION_ID": "your-organization-id", "GRAPHLIT_ENVIRONMENT_ID": "your-environment-id", "GRAPHLIT_JWT_SECRET": "your-jwt-secret" }, "type": "stdio" } } } Copy config	{ "mcpServers": { "agentset": { "command": "npx", "args": ["-y", "@agentset/mcp@latest", "--ns", "ns_xxx"], "env": { "AGENTSET_API_KEY": "agentset_xxx" } } } } Copy config	{ "mcpServers": { "cyanheads-obsidian": { "command": "npx", "args": ["-y", "obsidian-mcp-server@latest"], "env": { "MCP_TRANSPORT_TYPE": "stdio", "OBSIDIAN_API_KEY": "{obsidian-local-rest-api-key}", "OBSIDIAN_READ_ONLY": "true" } } } } Copy config	{ "mcpServers": { "omnisearch": { "command": "npx", "args": [ "mcp-omnisearch" ], "env": { "TAVILY_API_KEY": "your-tavily-key", "KAGI_API_KEY": "your-kagi-key", "BRAVE_API_KEY": "your-brave-key", "GITHUB_API_KEY": "your-github-token", "EXA_API_KEY": "your-exa-key", "LINKUP_API_KEY": "your-linkup-key", "FIRECRAWL_API_KEY": "your-firecrawl-key" }, "type": "stdio" } } } Copy config
Citations	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationdocs.agentset.ai Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →	Source repositorygithub.com 2026-07-21T07:17:01+00:00 Documentationraw.githubusercontent.com Submitted by oktofeesh12026-06-06 Source methodology →
Claim	Unclaimed	Unclaimed	Unclaimed	Unclaimed