SoloTerm Docs MCP
Remote MCP server for SoloTerm/Solo documentation, providing search and execute tools to query and interact with the docs API using JavaScript async arrow functions in isolated workers.
README
SoloTerm Docs MCP
Remote MCP server for SoloTerm/Solo documentation, built on Cloudflare Workers with the Agents SDK MCP handler and a Code Mode-style tool surface.
The /mcp endpoint exposes only two JavaScript-oriented tools:
search: run a JavaScript async arrow function against the generateddocsarray. The code runs in an isolated Dynamic Worker with outbound network access blocked.execute: run a JavaScript async arrow function againstsoloterm.request(). The code runs in an isolated Dynamic Worker whose outbound access is restricted tohttps://soloterm.com/api/v1/docsand child routes.
There are no legacy docs tools or MCP resources. ?codemode=false is intentionally ignored so clients always receive the same search and execute tools.
Generated Docs
The docs snapshot is generated into src/generated/docs.ts from https://soloterm.com/api/v1/docs.
The Code Mode declarations shown in tool descriptions are generated into src/generated/code-mode-types.ts by the same generator. They define the in-sandbox docs, generatedAt, sourceBaseUrl, and soloterm.request() API.
At runtime, search uses a cached live docs snapshot. The Worker refreshes that cache hourly with a Cloudflare scheduled trigger (0 * * * *) and also refreshes on cache miss. If the live docs API is unavailable during refresh, the generated static snapshot remains as a fallback.
Coverage is verified against two live sources:
- The docs API link graph starting at
https://soloterm.com/api/v1/docs. - Public docs URLs listed in
https://soloterm.com/sitemap.xml.
npm run docs:verify refreshes the snapshot, crawls the live API graph, reads the sitemap, and fails unless the generated slugs exactly cover the union of both indexes.
Development
npm install
npm run docs:fetch
npm run docs:verify
npm run build
npm run dev
MCP_URL=http://localhost:8787 npm run test:mcp
The local MCP endpoint is served at:
http://localhost:8787/mcp
Live Worker
https://soloterm-docs-mcp.sdf-ecosystem.workers.dev/mcp
Deploy
npm run deploy
After deploy, connect MCP clients to:
https://soloterm-docs-mcp.<your-subdomain>.workers.dev/mcp
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.