seta

Seta MCP is an offline-capable documentation-oriented MCP server designed to feed your LLM with localized Apex, LWC, and Salesforce configuration documentation. It reads a local directory structure you provide via LOCAL_DOCS_PATH and uses richly structured manifest.json files to organize libraries, topics, and semantic groups. Tools exposed by the server include get-library-id, which searches manifest.json files to find libraries matching your query, and get-library-docs, which fetches the content of a specific document file from your local filesystem. Additionally, you can optionally run a semantic indexer (seta-indexer) to create a vector store for semantic search, enabling more intuitive discovery of relevant documentation even when exact keywords don’t match. When used with an MCP client in your editor (e.g., VSCode, Cursor), you can prompt with phrases like use latest Apex docs or use seta to retrieve targeted documentation, and the server will provide context from the configured local docs.

Prerequisites:

• Node.js v18+ installed on your machine
• A local directory containing documentation structured as described (LOCAL_DOCS_PATH)
• An MCP client (e.g., VSCode MCP extension) to interact with the server

1. Clone the repository (or obtain the package that exposes the seta MCP server).

2. Install dependencies:

   • npm i

3. Prepare local documentation:

   • Create a folder for your docs and set LOCAL_DOCS_PATH to its absolute path. Each library folder must contain a manifest.json and related content as described in the README.

4. Run the MCP server:

   • The following command runs the server via npx (as configured in mcp_config):

   npx -y seta-mcp@latest

5. Verify operation:

   • Connect your MCP client to the running server and test tools like get-library-id and get-library-docs against your LOCAL_DOCS_PATH.

6. Optional: Build or develop locally if you are modifying the server code. Follow the repository’s development instructions for building TypeScript sources into dist/ and ensure the main server entry is accessible via the configured command.

Tips and common issues:

• Ensure LOCAL_DOCS_PATH is set and points to a real directory containing library subfolders with manifest.json files.
• Your manifest.json must follow the enhanced format described in the README to enable full topic metadata and semantic grouping.
• If you add new libraries or topics, run seta-indexer (if you’re using semantic search) to refresh the index.
• If you encounter connectivity issues with your MCP client, verify that the server command started correctly and that the client is configured to reach the running process (same machine/port assumptions as typical MCP setups).
• Environment variables you may commonly configure include LOCAL_DOCS_PATH (required for testing) and DEFAULT_MAX_TOKENS (optional) to control response length.