Seta MCP - Up-to-date Local Docs for Coding

Created By
techformista year ago
MCP server powered by local documentation
Overview

what is Seta MCP?

Seta MCP is a Model Context Protocol (MCP) server designed to assist Salesforce developers by providing up-to-date local documentation for coding and configuration tasks.

how to use Seta MCP?

To use Seta MCP, set the LOCAL_DOCS_PATH environment variable to point to your local documentation directory, organize your documentation into subdirectories with a manifest.json file, and run the server locally or host it remotely.

key features of Seta MCP?

  • Works entirely offline, ensuring privacy and control over documentation.
  • Allows fine-grained control over documentation versions and content.
  • Supports quick iteration on documentation with immediate availability to your AI assistant.

use cases of Seta MCP?

  1. Assisting developers with Salesforce Apex and LWC documentation.
  2. Providing context-aware documentation retrieval for coding tasks.
  3. Enabling offline access to proprietary or internal documentation.

FAQ from Seta MCP?

  • Can Seta MCP work with any documentation format?

Yes! As long as the documentation is structured correctly with a manifest.json, it can work with various formats.

  • Is Seta MCP free to use?

Yes! Seta MCP is open-source and free to use.

  • How do I ensure my documentation is accessible?

Make sure your LOCAL_DOCS_PATH is correctly set and that each library has a valid manifest.json.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
techformist
Star
1
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)

a day ago